Tatum Blockchain Data API

Name: Tatum Blockchain Data API API
Brand: Tatum Blockchain Data API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey8 EndpointsREST

For Agents

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

Quickstart

Get started with Tatum Blockchain Data 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:
"get token data by contract address"

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

Capabilities

What an agent can do with Tatum Blockchain Data API API.

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

GET STARTED

Start building with Tatum Blockchain Data API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Tatum Blockchain Data API API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

8 endpoints — tatum blockchain data api providing access to token data, wallet balances, nft collections, transactions, and staking information across 20+ blockchain networks.

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

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

Why though Jentic?

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

Credential isolation

Tatum Blockchain Data API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get token data by contract address') and Jentic returns the matching Tatum Blockchain Data API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Tatum Blockchain Data API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Tatum Blockchain Data API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.