Algod REST API

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

★ Only Publicly Available SpecFinanceBankingapiKey56 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.

Quickstart

Get started with Algod REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up an Algorand account"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Algod REST API 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}

Look up Algorand Standard Asset (ASA) metadata by asset ID via /v2/assets/{asset-id}

GET STARTED

Start building with Algod REST API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to look up the balance of an Algorand address, Retrieve the assets held by a specific account, Get the latest block on the Algorand mainnet, Find the application state for a smart contract by ID

Not supported: Does not handle historical indexed queries, off-chain pricing, or wallet key management - use the Algorand Indexer, exchange APIs, or local wallet libraries for those. Use this API for direct node-level reads and transaction submission only.

Jentic publishes the only available OpenAPI specification for Algod REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the Algod REST API, keeping it validated and agent-ready. The Algod API is the primary interface to an Algorand node, exposing 56 endpoints for reading account state, application and asset data, blocks, and ledger deltas, plus submitting transactions and running TEAL programs. It is the lowest-level on-chain interface for Algorand and is what wallets, dApps, and indexers call to interact with the network. Public infrastructure like AlgoNode hosts mainnet and testnet endpoints under the same spec.

Use Cases

Patterns agents use Algod REST API 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 though Jentic?

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

Credential isolation

X-Algo-API-Token is stored encrypted in the Jentic vault. Agents receive scoped tokens at request time; the raw API token never enters agent context, so a leaked agent log cannot expose node access.

Intent-based discovery

Agents search Jentic by intent (e.g. 'look up Algorand account' or 'submit Algorand transaction') and Jentic returns the matching Algod operation with its input schema.

Time to first call

Direct integration: 1-2 days to wire account reads, transaction submission, and confirmation polling. Through Jentic: under 30 minutes - search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ethereum JSON-RPC API

Equivalent node-level interface for the Ethereum blockchain

Choose Ethereum when the use case targets EVM-compatible chains rather than Algorand.

Alternative

Alchemy API

Multi-chain blockchain infrastructure with enhanced indexer endpoints

Choose Alchemy for multi-chain support and indexer-style queries Algod does not offer.

Complementary

Binance API

Centralized exchange where ALGO and ASAs trade

Use Binance for off-chain price discovery and order placement that complements on-chain reads from Algod.

FAQs

Specific to using Algod REST API 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 at https://app.jentic.com/sign-up.

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.