Zerion
Zerion is an Ethereum and Solana wallet and developer platform focused on making onchain data easy to use. The Zerion API delivers clean, normalized wallet data, token analytics, DeFi positions, transaction history, PnL, NFTs, gas prices, swap and bridge quotes, and real-time transaction webhooks across EVM chains and Solana. The same infrastructure powers the Zerion wallet app used by millions. It is a JSON:API REST service with HTTP Basic (API key) authentication plus pay-per-request x402 (Base/Solana USDC) and MPP (Tempo USDC) options aimed at AI agents, an open-source CLI, six packaged agent skills, a hosted MCP server, and Kafka streaming for high-throughput pipelines.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Zerion the way a machine reads it — 19 machine-readable artifacts across 9 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 — Zerion scores 61.9/100 (strong), with a separate agent-readiness read of 82/100 (agent native). 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 Zerion
Each block below is one kind of artifact we hold for Zerion. 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 9
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.
Zerion chains API
Operations related to chains, such as list all chains.
Zerion dapps API
Operations related to decentralized applications, such as list them all, search or get by ID.
Zerion fungibles API
Operations related to fungible assets, such as list them all, search or get by ID.
Zerion gas API
Operations related to gas.
Zerion nfts API
Operations related to non fungible assets, such list them, search or get by ID.
Zerion subscriptions to transactions API
Operations related to subscriptions to transactions.
Zerion swap API
Operations related to swapping and bridging assets.
Zerion wallet sets API
Operations on a wallet set — aggregated portfolio data across at most one EVM address and one Solana address queried together.
Zerion wallets API
Operations related to wallets, such as portfolio charts, positions, and transactions.
Scroll within the panel for all 9 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOZerion wallet activity subscription
Create a transaction webhook subscription for a set of wallets, confirm it, then verify the watched-wallet count.
ARAZZOZerion wallet overview
Pull a wallet's portfolio, positions, transaction history, and PnL in one flow.
ARAZZOMCP 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.
zerion-mcp.yml
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.
Zerion 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.
Zerion Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Zerion Transactions Webhooks
ASYNCAPISecurity 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 Zerion — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zerion · machine-readable index on apis.io