IOTA
IOTA is an open-source distributed ledger technology built to bring real-world applications on-chain. It is the first internet-scale programmable blockchain platform powered by the Move programming language with horizontal scaling, feeless transactions, and a unique parallel transaction processing model. IOTA exposes a JSON-RPC 2.0 API over HTTP and a GraphQL RPC for querying objects, checkpoints, transactions, coins, events, and on-chain state on Mainnet, Testnet, and Devnet networks. The platform targets trade and supply chains, decentralized finance, digital identity, real-world asset tokenization, and product lifecycle management.
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 IOTA the way a machine reads it — 41 machine-readable artifacts across 17 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 — IOTA scores 54.6/100 (developing), 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.
How we profile IOTA
Each block below is one kind of artifact we hold for IOTA. 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 17
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.
IOTA GraphQL API
GraphQL RPC interface for the IOTA blockchain, providing an alternative to the JSON-RPC API. Supports querying transaction blocks, objects, checkpoints, events, and on-chain sta...
IOTA auth API
The auth API from IOTA — 2 operation(s) for auth.
IOTA chains API
The chains API from IOTA — 18 operation(s) for chains.
IOTA Coin Query API
Coin and balance queries: balances, coins list, metadata, supply
IOTA corecontracts API
The corecontracts API from IOTA — 18 operation(s) for corecontracts.
IOTA Extended API
Indexer-exclusive methods for advanced queries, events, dynamic fields, IOTA Names
IOTA Governance API
Governance, staking, validator, epoch, and system state queries
IOTA Health API
The Health API from IOTA — 1 operation(s) for health.
IOTA metrics API
The metrics API from IOTA — 3 operation(s) for metrics.
IOTA Move Utils API
Move smart contract introspection: modules, functions, structs
IOTA node API
The node API from IOTA — 11 operation(s) for node.
IOTA Read API
Core read operations: objects, checkpoints, transactions, events, protocol config
IOTA requests API
The requests API from IOTA — 1 operation(s) for requests.
IOTA Transaction Builder API
Build unsigned transactions for transfers, staking, Move calls (unsafe_ prefix)
IOTA users API
The users API from IOTA — 4 operation(s) for users.
IOTA Write API
Transaction execution, dry run, and dev inspection
IOTA Ws API
The Ws API from IOTA — 1 operation(s) for ws.
Scroll within the panel for all 17 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
IOTA GraphQL API
The IOTA GraphQL RPC provides a flexible, typed interface for querying on-chain state on the IOTA blockchain. It serves as an alternative to the JSON-RPC 2.0 API and is served b...
GRAPHQLPricing 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.
Iota 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.
Iota 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.
Iota Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
JSON-RPC 2.0 over HTTP
Standard JSON-RPC 2.0 protocol over HTTP POST to IOTA full nodes and indexers
GraphQL RPC
GraphQL interface as an alternative to JSON-RPC for flexible on-chain data queries
Three Network Environments
Mainnet (production), Testnet (testing), and Devnet (development) environments with faucets
Move Smart Contracts
Asset-oriented Move programming language for type-safe, resource-oriented smart contracts
EVM Layer 2
Ethereum-compatible EVM Layer 2 chain enabling Solidity contract deployment and tooling reuse
No Authentication Required
Public endpoints are open and require no API key for development and testing use
Cursor-based Pagination
All list endpoints support cursor-based pagination for efficient data traversal
BCS Binary Encoding
Binary Canonical Serialization (BCS) support alongside JSON for efficient data transfer
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Iota Context
JSON-LDSecurity 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.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
DeFi Application Backend
Query coin balances, object states, and submit transactions for decentralized finance apps on IOTA
Supply Chain Traceability
Track real-world assets and product lifecycle data on the IOTA distributed ledger
Digital Identity
Manage decentralized identifiers (DIDs) and verifiable credentials on-chain
Real-World Asset Tokenization
Tokenize and manage traditional financial assets bridged to IOTA using Move smart contracts
Blockchain Analytics
Query checkpoints, transaction blocks, and events for real-time analytics and data pipelines
Wallet Development
Check coin balances, fetch transaction history, build and submit signed transactions
Smart Contract Development
Introspect Move modules, deploy packages, and interact with on-chain programs via Move Utils
EVM dApp Migration
Deploy existing Solidity smart contracts on IOTA EVM Layer 2 using standard Ethereum tooling
Scroll within the panel for all 8 ·
Resources
Every other property we hold for IOTA — 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 2
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
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/iota · machine-readable index on apis.io