How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Hiro website screenshot

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.

agent ready

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Hiro the way a machine reads it — 57 machine-readable artifacts across 4 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 29.0/100 (thin), with a separate agent-readiness read of 31/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Hiro Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Hiro's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hiro/"
   title="Hiro on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/hiro.svg"
       alt="Hiro Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

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 ·

Open Collections 25

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 25 ·

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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Hiro Plans Pricing

3 plans

PLANS

Rate 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

2 limits

RATE LIMITS

FinOps 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

FINOPS

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

Hiro Authentication

apiKey · 1 scheme

SECURITY

Hiro Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

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.

Hiro Agentic Access

154 operations · 14 acting

154 operations · 14 acting

AGENTIC

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

Where this information came from

This is an independent, third-party profile of Hiro, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.