Hiro
Hiro builds developer tooling for Bitcoin and the Stacks layer. Provides REST APIs (Stacks Blockchain API, Token Metadata API, Signer Metrics API, Chainhooks API, Platform API), Stacks Node JSON-RPC, plus the Hiro Platform for managing devnets and chainhooks.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Hiro the way a machine reads it — 32 machine-readable artifacts across 26 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 — Hiro scores 36.5/100 (thin), with a separate agent-readiness read of 48/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 Hiro
Each block below is one kind of artifact we hold for Hiro. 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 26
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.
Hiro Chainhooks API
REST API for Chainhook predicate registration and event streaming for Bitcoin and Stacks.
Hiro Platform API
REST API to programmatically manage Hiro Platform devnets and chainhooks.
Hiro Accounts API
Read-only endpoints to obtain Stacks account details
Hiro Atlas API
Operations related to the Atlas global namespace.
Hiro Blocks API
The Blocks API from Hiro — 37 operation(s) for blocks.
Hiro Blocks Proposals API
The Blocks Proposals API from Hiro — 2 operation(s) for blocks proposals.
Hiro Burn Blocks API
Read-only endpoints to obtain burn block details
Hiro Faucets API
Endpoints to request STX or BTC tokens (not possible on Mainnet)
Hiro Fees API
Read-only endpoints to obtain fee details
Hiro Fungible Tokens API
The Fungible Tokens API from Hiro — 1 operation(s) for fungible tokens.
Hiro Info API
Read-only endpoints to obtain network, Proof-of-Transfer, Stacking, STX token, and node information
Hiro Mempool API
Endpoints to obtain Mempool information
Hiro Microblocks API
Read-only endpoints to obtain microblocks details
Hiro Mining API
Endpoints related to Stacks block production and mining.
Hiro Names API
Read-only endpoints realted to the Blockchain Naming System on Stacks
Hiro Non-Fungible Tokens API
Read-only endpoints to obtain non-fungible token details
Hiro Proof of Transfer API
Endpoints to get information about the Proof of Transfer consensus mechanism
Hiro Search API
Read-only endpoints to search for accounts, blocks, smart contracts, and transactions
Hiro Signers API
The Signers API from Hiro — 4 operation(s) for signers.
Hiro Smart Contracts API
Read-only endpoints to obtain Clarity smart contract details
Hiro StackerDB API
Endpoints for interacting with StackerDB instances.
Hiro Stacking API
The Stacking API from Hiro — 4 operation(s) for stacking.
Hiro Stacking Rewards API
Read-only endpoints to obtain Stacking reward details
Hiro Status API
Service status endpoints
Hiro Tokens API
Token metadata endpoints
Hiro Transactions API
Endpoints to obtain transaction details and to broadcast transactions to the network
Scroll within the panel for all 26 ·
Pricing 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.
Hiro Plans Pricing
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.
Hiro 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.
Hiro Finops
FINOPSSecurity Posture 2
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 Hiro — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
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
← All providers · Data indexed from github.com/api-evangelist/hiro · machine-readable index on apis.io