> For the complete documentation index, see [llms.txt](https://docs.tetreum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tetreum.com/api-archive/api-archive.md).

# API Archive

Blockscout-style legacy API references preserved for backward compatibility and migration purposes.

If you are still using older per-instance routes or legacy integrations, update your applications to the current Tetreum Testnet endpoints where applicable.

### Archived API References

1. **REST API**\
   API used by the explorer frontend and related services.
2. **RPC API**\
   Compatibility-oriented API for developers migrating applications from Etherscan-style integrations.
3. **ETH RPC API**\
   Supports common Ethereum JSON-RPC methods for EVM-compatible integrations.
4. **GraphQL API**\
   GraphQL interface for querying explorer and blockchain data.
5. **Contract Verification API**\
   Legacy contract verification reference.
6. **Additional Integration APIs**\
   Archived or special-purpose developer integration references.

### Notes

* Tetreum Testnet is a **Geth-based PoA** and **EVM-compatible** network
* Legacy API references are provided for documentation continuity
* New integrations should use the current Tetreum Testnet endpoints and latest docs
* Public RPC URL: `https://testrpc.tetreum.com`
* Explorer URL: `https://testnet.tetscan.com/`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tetreum.com/api-archive/api-archive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.