Algorand Algod REST API

Name: Algod REST API
Brand: Algod REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey56 EndpointsREST

For Agents

Read on-chain state and submit transactions on the Algorand blockchain - accounts, applications (smart contracts), assets, blocks, ledger deltas, and TEAL execution.

Install Jentic One Beta

Connect the Algod REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Algod REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Algod REST API.

Look up account balances, assets, and applications via /v2/accounts/{address}

Inspect Algorand smart contracts (applications) including their boxes via /v2/applications/{application-id} and /v2/applications/{application-id}/boxes

Retrieve any block by round number along with its transactions and state proofs via /v2/blocks/{round}

GET STARTED

Start building with Algod REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Algod REST API for, with concrete tasks.

★ Wallet balance and asset lookup

Query /v2/accounts/{address} to fetch ALGO balance, opted-in assets with quantities, and any applications the account participates in. The same endpoint returns minimum balance requirements and reward state, so wallets can show a complete portfolio view in a single call.

GET /v2/accounts/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA to fetch ALGO balance and asset list

Smart contract state and box reads

Inspect Algorand applications by calling /v2/applications/{application-id} for global state and /v2/applications/{application-id}/boxes plus /v2/applications/{application-id}/box for box storage. Useful for dApp dashboards that need to render live smart contract state without running an indexer.

GET /v2/applications/123456 and GET /v2/applications/123456/boxes to enumerate the contract's global state and box keys

Transaction submission and confirmation

After signing a transaction client-side, post the binary blob to the transactions endpoint and poll /v2/accounts/{address}/transactions/pending to track confirmation. Combined with /v2/blocks/{round} an agent can wait for a specific round and verify inclusion before reporting success.

POST the signed transaction blob to the transactions endpoint, then poll /v2/accounts/{sender}/transactions/pending until the txid disappears or appears confirmed in /v2/blocks/{round}

Agent-driven on-chain reads in chat assistants

An AI assistant connecting through Jentic can answer questions like 'what assets does this address hold' or 'is my transaction confirmed yet' by hitting the Algod API. Jentic resolves intents to AccountInformation or pending-transactions endpoints and injects the API token from the vault.

Search Jentic for 'look up Algorand account', load AccountInformation, and execute with the user's address

Key Endpoints

56 endpoints — jentic publishes the only available openapi specification for the algod rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v2/accounts/{address}

Get account information including balance and assets

GET

/v2/accounts/{address}/assets

List assets held by an account

GET

/v2/applications/{application-id}

Get application (smart contract) state

GET

/v2/applications/{application-id}/boxes

List boxes for an application

GET

/v2/assets/{asset-id}

Get an Algorand Standard Asset by ID

GET

/v2/blocks/{round}

Get a block by round number

GET

/v2/accounts/{address}/transactions/pending

List pending transactions for an account

GET

/v2/accounts/{address}

Get account information including balance and assets

GET

/v2/accounts/{address}/assets

List assets held by an account

GET

/v2/applications/{application-id}

Get application (smart contract) state

GET

/v2/applications/{application-id}/boxes

List boxes for an application

GET

/v2/assets/{asset-id}

Get an Algorand Standard Asset by ID

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Algod API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an Algorand account balance' or 'look up an asset by id', and Jentic returns the matching Algod operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Algod REST API through Jentic.

Why is there no official OpenAPI spec for the Algod REST API?

Algorand publishes API documentation but does not host a packaged OpenAPI 3.0 specification suitable for agent tooling. Jentic generates and maintains this spec so that AI agents and developers can call the Algod REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Algorand Algod REST API use?

An API key passed in the X-Algo-API-Token header. Public providers like AlgoNode (mainnet-api.algonode.cloud) accept an empty token for anonymous read access; private nodes and paid providers issue per-account tokens. Through Jentic, the token is stored in the vault and injected at request time.

Can I submit transactions through this API?

Yes. After signing a transaction client-side with an Algorand SDK, submit the binary blob to the transactions endpoint. Use /v2/accounts/{address}/transactions/pending to track confirmation, and /v2/blocks/{round} to verify inclusion in a specific round.

What are the rate limits for the Algod REST API?

Limits depend on the node operator. AlgoNode publishes free-tier limits per IP and offers higher tiers via subscription. Private nodes have no shared limits. Plan for 429 responses and back off using the Retry-After header where present.

How do I query an Algorand account through Jentic?

Search Jentic for 'look up Algorand account', load AccountInformation, and execute with the address. Jentic injects X-Algo-API-Token from the vault and calls /v2/accounts/{address} - no manual auth wiring needed.

Does the Algod API include indexer-style queries?

No. Algod serves current and recent state directly from a node; for historical queries (transactions older than the node's catchup window, or filtered by sender, asset, etc.) use the separate Algorand Indexer API.

Can I limit what my agent is allowed to do with the Algod REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Algod operations and credentials the agent may use. The Algod REST API takes the account address, asset id, or application id in the URL path (/v2/accounts/{address}, /v2/assets/{asset-id}, /v2/applications/{application-id}), so you can pin the agent to a single account or asset. You also choose the operations it may call, so you can keep it to node-level reads and exclude transaction submission unless you add it.