API profile

Tatum

Tatum is tracked as a multichain Provider Profile for indexed blockchain data, RPC node access, notifications, and wallet-oriented API workflows. PubFi Discovery treats this as public profile evidence only and does not assert PubFi gateway availability

Coming soonNeeds re-verification

Decision guide

Use it when

Multichain app teams that want one API platform for RPC, indexed data, notifications, and wallet workflows

Check first

Anonymous browser-only calls without account setup

PubFi status

Needs re-verification

The editorial profile remains useful, but its public evidence is degraded. Reverify upstream docs and commercial terms; use the live Registry and runtime OpenAPI for PubFi execution decisions.

Key facts

Auth
API key
Pricing
Freemium
Agent actionability
Editorial revalidation required; runtime status separate
PubFi gateway
Live Registry unavailable
Last verified

Provider-sourced facts

Primary query
tatum api Source
Primary coverage
RPC node access, indexed blockchain data, notifications, and wallet-oriented API workflows across many chains Source
Supported chains evidence
Official docs list many supported blockchains, including Bitcoin, Ethereum, Polkadot, Polygon, Solana, Tron, and other networks. Source
Auth model
Tatum uses API-key-backed dashboard access for production API use. Source
Commercial fact
Public pricing lists a free account plus paid dedicated API-key throughput tiers, including a 10 RPS dedicated key tier at $99/month. Source
PubFi status
PubFi Discovery tracks Tatum as a public Provider Profile only; this profile does not assert a PubFi gateway route, adapter certification, or credential availability. Source

Best fit and tradeoffs

Best for

  • Multichain app teams that want one API platform for RPC, indexed data, notifications, and wallet workflows
  • Teams comparing managed blockchain data APIs with wallet and notification features
  • Backend services that can manage provider API keys server-side
  • They want a public starting point for evaluating Tatum API documentation.
  • They need to compare Tatum against nearby crypto data providers before runtime integration work.
  • They want claim-safe evidence that can be promoted later when adapter certification exists.

Watchouts

  • Anonymous browser-only calls without account setup
  • Teams that need a PubFi-certified gateway route today
  • Single-purpose market-data feeds where a narrower provider may be easier to evaluate
  • Automation-built profiles may have incomplete category, pricing, quota, or endpoint coverage until deeper docs parsing runs.
  • Public docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, and terms before treating the provider as production-callable.

Why teams choose it

Tatum API is an automation-built Provider Profile based on public API corpus evidence. It helps teams inspect Tatum docs, product naming, and on chain state fit before any runtime adapter or commercial approval work begins.

Discovery keeps this page claim-safe: inclusion means public evidence was processed into a Provider Profile, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, or supplier procurement for Tatum.

What it can cover

Tatum API on chain state evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Bitcoin, Ethereum, Solana
Output contracts
Chain State Record

Quick start

RESTEndpoint path not listed
Style
REST
Language
HTTP
Method
Not listed
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

PubFi gateway

Live Registry unavailable

PubFi could not verify the active signed Registry generation. Checked-in Discovery content is not execution authority, so this page fails closed instead of inferring a gateway route.

Runtime status
registry_unavailable
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Retry the live Registry view or inspect the runtime OpenAPI before execution.
  • Do not infer availability from provider documentation, product copy, or repository data.

Implementation notes

Docs

Medium

Review Tatum public docs and authentication requirements before any adapter certification work starts.

Coverage

Medium

Treat the current Tatum API profile as processed evidence, not as complete coverage of every chain, endpoint, or product surface.

Schema

Low

Use endpoint-specific docs evidence before deriving runtime request or response contracts.

Use cases

  • Compare multichain blockchain data and RPC coverage against Moralis, Covalent, and QuickNode
  • Evaluate wallet-ledger and notification workflows that need provider-managed auth
  • Plan API-key-backed backend integrations without assuming PubFi gateway availability

Comparison snapshot

Tatum API should be compared with providers that cover similar on chain state workflows. The current automation output is enough for Discovery visibility and follow-up triage, but not for certified gateway routing.

PubFi friction relief

Docs

Source friction
Tatum public docs are available as public documentation evidence.
PubFi relief
PubFi Discovery turns the public evidence into a claim-safe Provider Profile and separates it from gateway certification.

FAQ

What is Tatum used for?

Tatum is used for multichain blockchain application workflows, including RPC node access, indexed data reads, notifications, and wallet-related API operations.

Does Tatum require authentication?

Yes. Production API use is account and API-key based; Discovery keeps that authentication requirement visible rather than treating the provider as anonymously callable.

Is Tatum available through the PubFi gateway?

No. This page is a public Provider Profile and does not claim a PubFi gateway route, adapter certification, or upstream credential.