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

# Endless APIs

The Endless Blockchain network can be accessed by several APIs, depending on your use-case.

1. Endless **Fullnode-embedded REST API.**

   This API - embedded into Fullnodes - provides a simple, low latency, yet low-level way of *reading* state and *submitting* transactions to the Endless Blockchain. It also supports transaction simulation.
2. Endless **Indexer-powered Restful API.**

   This API provides a high-level, opinionated Restful API to *read* state from the Endless Blockchain. If your app needs to interact with high level constructs, such as Tokens, NFTs, Endless Objects or custom Move contracts, you likely want to incorporate the Endless Indexer API in some fashion.
3. Endless **GRPC Transaction Stream API**

   This API provides a way to stream historical and current transaction data in real-time to an indexing processor. This API is used by the Endless Core Indexing infrastructure itself but also can be used to build app-specific custom indexing processors that process blockchain data in real-time.


---

# 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.endless.link/endless/devbuild/build/endless-apis.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.