canonical: https://jentic.com/apis/tatum.io/tatum

# Tatum Blockchain Data API

Tatum blockchain data API providing access to token data, wallet balances, NFT collections, transactions, and staking information across 20+ blockchain networks. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get token data by contract address, get wallet balances at a specific blockchain moment. Covers 8 operations with apiKey authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Get token data by contract address
- Manage payments data programmatically
- Integrate Tatum Blockchain Data API into automated workflows
- Query and filter Tatum Blockchain Data API records by parameters
- Monitor Tatum Blockchain Data API operational status and events

## Use cases

### Payments Operations

Use the Tatum Blockchain Data API to perform payments operations programmatically. The API provides 8 endpoints covering core functionality including get token data by contract address, get wallet balances at a specific blockchain moment, get wallet portfolio overview.

Example prompt: Call GET /tokens to get token data by contract address

### Automated Collections Management

Automate collections operations by combining multiple Tatum Blockchain Data API endpoints. Agents can get wallet balances at a specific blockchain moment and then get wallet portfolio overview in a single workflow.

Example prompt: Call GET `/wallet/balance/time` to get wallet balances at a specific blockchain moment, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tatum Blockchain Data API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get token data by contract address', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/tokens` | Get token data by contract address |
| GET | `/wallet/balance/time` | Get wallet balances at a specific blockchain moment |
| GET | `/wallet/portfolio` | Get wallet portfolio overview |
| GET | `/wallet/utxo` | Get unspent UTXOs for a wallet |
| GET | `/collections` | Get tokens from an NFT collection |
| GET | `/transactions/hash` | Get transactions by hash |
| GET | `/transactions` | Get transaction history for addresses |
| GET | `/staking/native/current-assets` | Get current staked assets for an address |

## Key resources

- **Collections** — Operations for collections
- **Staking** — Operations for staking
- **Tokens** — Operations for tokens
- **Transactions** — Operations for transactions
- **Wallet** — Operations for wallet

## Why Jentic

- **Setup:** Wiring the Tatum Blockchain Data API by hand means sending its x-api-key header on every request, targeting the api.tatum.io/v4/data host, and building your own retry handling across its data endpoints. Through Jentic you install once, import the Tatum Blockchain Data API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Tatum Blockchain Data API's listed operations are read-only lookups where the target travels as query parameters, so limit the agent to the operations it needs, such as fetching token data or a wallet portfolio. You choose what it may call, and these endpoints only read data, so nothing that changes state is included.
- **Credential handling:** Your Tatum 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.
- **Discovery method:** Agents search Jentic by intent such as 'get token data by contract address' or 'check a wallet balance', and Jentic returns the matching Tatum Blockchain Data API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Tatum Blockchain Data API use?

The Tatum Blockchain Data API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get token data by contract address with the Tatum Blockchain Data API?

Yes. Use the GET /tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tatum Blockchain Data API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get token data by contract address through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get token data by contract address'. Jentic returns the matching Tatum Blockchain Data API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tatum Blockchain Data API have?

The Tatum Blockchain Data API exposes 8 endpoints covering collections, staking, tokens operations.

### Can I limit what my agent is allowed to do with the Tatum Blockchain Data API?

Yes. Because Jentic One is self-hosted, you decide which Tatum Blockchain Data API operations your agent may call and which credentials it may use. Every listed endpoint is a read-only lookup, so you can restrict the agent to just the calls it needs, such as GET /tokens for token data or GET `/wallet/portfolio` for a wallet overview, while leaving out others like transaction history or staking. Since these endpoints only read data and never change state, the agent cannot alter anything with this API.