Hedera
Hedera is an enterprise-grade public distributed ledger platform built for the digital economy and governed by a council of leading global institutions. The Hedera Mirror Node REST API provides read-only access to historical network data including transactions, accounts, tokens, NFTs, smart contracts, consensus topics, blocks, schedules, and network-level information. The public API requires no authentication and supports mainnet, testnet, and previewnet environments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Hedera the way a machine reads it — 209 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Hedera scores 51.7/100 (developing), with a separate agent-readiness read of 50/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hedera
Each block below is one kind of artifact we hold for Hedera. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Hedera accounts API
The accounts object represents the information associated with an account entity and returns a list of account information.The accounts list endpoint is cached and not updated a...
Hedera airdrops API
The airdrops API from Hedera — 2 operation(s) for airdrops.
Hedera balances API
The balance object represents the balance of accounts on the Hedera network.
Hedera blocks API
The blocks API from Hedera — 2 operation(s) for blocks.
Hedera contracts API
The contracts objects represents the information associated with contract entities.The contracts list endpoint is cached and not updated as frequently as the contract lookup by ...
Hedera network API
The network API from Hedera — 6 operation(s) for network.
Hedera schedules API
The schedules object represents the information associated with a schedule entity.The schedules list endpoints is cached and not updated as frequently as the schedule lookup by ...
Hedera tokens API
The tokens object represents the information associated with a token entity and returns a list of token information.The tokens list endpoint is cached and not updated as frequen...
Hedera topics API
The topics object represents the information associated with a topic entity and returns topic messages information.
Hedera transactions API
The transaction object represents the transactions processed on the Hedera network.
Scroll within the panel for all 10 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Hedera API Rules
SPECTRALJSON Schema 144
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessList
JSON SCHEMAAccountAlias
JSON SCHEMAAccountBalance
JSON SCHEMAAccountBalanceTransactions
JSON SCHEMAAccountInfo
JSON SCHEMAAccounts
JSON SCHEMAAccountsResponse
JSON SCHEMAAlias
JSON SCHEMAAllowance
JSON SCHEMAAssessedCustomFee
JSON SCHEMAAuthorizationList
JSON SCHEMABalance
JSON SCHEMABalancesResponse
JSON SCHEMABlock
JSON SCHEMABlocks
JSON SCHEMABlocksResponse
JSON SCHEMABloom
JSON SCHEMAChunkInfo
JSON SCHEMAConsensusCustomFees
JSON SCHEMAContract
JSON SCHEMAContractAction
JSON SCHEMAContractActions
JSON SCHEMAContractActionsResponse
JSON SCHEMAContractCallRequest
JSON SCHEMAContractCallResponse
JSON SCHEMAContractLog
JSON SCHEMAContractLogTopics
JSON SCHEMAContractLogs
JSON SCHEMAContractLogsResponse
JSON SCHEMAContractResponse
JSON SCHEMAContractResult
JSON SCHEMAContractResultDetails
JSON SCHEMAContractResultLog
JSON SCHEMAContractResultLogs
JSON SCHEMAContractResultStateChange
JSON SCHEMAContractResultStateChanges
JSON SCHEMAContractResults
JSON SCHEMAContractResultsResponse
JSON SCHEMAContractState
JSON SCHEMAContractStateResponse
JSON SCHEMAContracts
JSON SCHEMAContractsResponse
JSON SCHEMACryptoAllowance
JSON SCHEMACryptoAllowances
JSON SCHEMACryptoAllowancesResponse
JSON SCHEMACustomFeeLimit
JSON SCHEMACustomFees
JSON SCHEMAEntityId
JSON SCHEMAEntityIdQuery
JSON SCHEMAError
JSON SCHEMAEthereumHash
JSON SCHEMAEvmAddress
JSON SCHEMAEvmAddressNullable
JSON SCHEMAEvmAddressWithShardRealm
JSON SCHEMAExchangeRate
JSON SCHEMAFeeEstimate
JSON SCHEMAFeeEstimateMode
JSON SCHEMAFeeEstimateNetwork
JSON SCHEMAFeeEstimateResponse
JSON SCHEMAFeeExtra
JSON SCHEMAFixedCustomFee
JSON SCHEMAFixedFee
JSON SCHEMAFractionalFee
JSON SCHEMAHederaHash
JSON SCHEMAHook
JSON SCHEMAHookStorage
JSON SCHEMAHooksResponse
JSON SCHEMAHooksStorageResponse
JSON SCHEMAKey
JSON SCHEMALinks
JSON SCHEMALogTopicQueryParam
JSON SCHEMANetworkExchangeRateSetResponse
JSON SCHEMANetworkFee
JSON SCHEMANetworkFees
JSON SCHEMANetworkFeesResponse
JSON SCHEMANetworkNode
JSON SCHEMANetworkNodes
JSON SCHEMANetworkNodesResponse
JSON SCHEMANetworkStakeResponse
JSON SCHEMANetworkSupplyResponse
JSON SCHEMANft
JSON SCHEMANftAllowance
JSON SCHEMANftAllowances
JSON SCHEMANftAllowancesResponse
JSON SCHEMANftTransactionHistory
JSON SCHEMANftTransactionTransfer
JSON SCHEMANfts
JSON SCHEMAOpcode
JSON SCHEMAOpcodesResponse
JSON SCHEMAPositiveNumber
JSON SCHEMARegisteredBlockNodeApi
JSON SCHEMARegisteredBlockNodeEndpoint
JSON SCHEMARegisteredGeneralServiceEndpoint
JSON SCHEMARegisteredMirrorNodeEndpoint
JSON SCHEMARegisteredNode
JSON SCHEMARegisteredNodeType
JSON SCHEMARegisteredNodes
JSON SCHEMARegisteredNodesResponse
JSON SCHEMARegisteredRpcRelayEndpoint
JSON SCHEMARegisteredServiceEndpoint
JSON SCHEMARegisteredServiceEndpoints
JSON SCHEMARoyaltyFee
JSON SCHEMASchedule
JSON SCHEMAScheduleSignature
JSON SCHEMASchedules
JSON SCHEMASchedulesResponse
JSON SCHEMAServiceEndpoint
JSON SCHEMAServiceEndpoints
JSON SCHEMAStakingReward
JSON SCHEMAStakingRewardTransfer
JSON SCHEMAStakingRewardTransfers
JSON SCHEMAStakingRewardsResponse
JSON SCHEMATimestamp
JSON SCHEMATimestampNullable
JSON SCHEMATimestampRange
JSON SCHEMATimestampRangeNullable
JSON SCHEMAToken
JSON SCHEMATokenAirdrop
JSON SCHEMATokenAirdrops
JSON SCHEMATokenAirdropsResponse
JSON SCHEMATokenAllowance
JSON SCHEMATokenAllowances
JSON SCHEMATokenAllowancesResponse
JSON SCHEMATokenBalance
JSON SCHEMATokenBalancesResponse
JSON SCHEMATokenDistribution
JSON SCHEMATokenInfo
JSON SCHEMATokenRelationship
JSON SCHEMATokenRelationshipResponse
JSON SCHEMATokens
JSON SCHEMATokensResponse
JSON SCHEMATopic
JSON SCHEMATopicMessage
JSON SCHEMATopicMessages
JSON SCHEMATopicMessagesResponse
JSON SCHEMATransaction
JSON SCHEMATransactionByIdResponse
JSON SCHEMATransactionDetail
JSON SCHEMATransactionDetails
JSON SCHEMATransactionId
JSON SCHEMATransactionIdStr
JSON SCHEMATransactionTypes
JSON SCHEMATransactions
JSON SCHEMATransactionsResponse
JSON SCHEMAScroll within the panel for all 144 ·
Examples 48
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Contractcall
EXAMPLEEstimatefees
EXAMPLEGetaccount
EXAMPLEGetaccounts
EXAMPLEGetbalances
EXAMPLEGetblock
EXAMPLEGetblocks
EXAMPLEGetcontract
EXAMPLEGetcontractactions
EXAMPLEGetcontractlogsbycontractid
EXAMPLEGetcontractopcodes
EXAMPLEGetcontractstate
EXAMPLEGetcontracts
EXAMPLEGetcontractslogs
EXAMPLEGetcontractsresults
EXAMPLEGetcryptoallowances
EXAMPLEGethookstorage
EXAMPLEGethooks
EXAMPLEGetnetworkexchangerate
EXAMPLEGetnetworkfees
EXAMPLEGetnetworknodes
EXAMPLEGetnetworkstake
EXAMPLEGetnetworksupply
EXAMPLEGetnft
EXAMPLEGetnftallowances
EXAMPLEGetnfttransactions
EXAMPLEGetnfts
EXAMPLEGetnftsbyaccountid
EXAMPLEGetoutstandingtokenairdrops
EXAMPLEGetpendingtokenairdrops
EXAMPLEGetregisterednodes
EXAMPLEGetschedule
EXAMPLEGetschedules
EXAMPLEGetstakingrewards
EXAMPLEGettoken
EXAMPLEGettokenallowances
EXAMPLEGettokenbalances
EXAMPLEGettokens
EXAMPLEGettokensbyaccountid
EXAMPLEGettopic
EXAMPLEGettopicmessagebytimestamp
EXAMPLEGettopicmessages
EXAMPLEGettransaction
EXAMPLEGettransactions
EXAMPLEScroll within the panel for all 48 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Hedera — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hedera · machine-readable index on apis.io