Kite
Kite (gokite.ai, formerly Zettablock) builds agentic payment infrastructure for the machine-to-machine economy. Kite Agent Passport gives autonomous AI agents their own identity, a funded wallet, user-set spending rules, delegated payment authority, and verifiable on-chain receipts, driven from a coding agent through the kpass and ksearch CLIs and a set of published Passport agent skills. Kite also operates Kite Chain, an EVM-compatible Avalanche-subnet Layer 1 (mainnet chain ID 2366, testnet 2368) with public HTTPS and WSS JSON-RPC endpoints, a stablecoin gasless transfer relayer built on EIP-3009 signed authorizations, and an x402 HTTP-402 payment surface with support for the Stripe/Tempo Machine Payments Protocol (MPP). Kite raised an $18M Series A led by PayPal Ventures and General Catalyst in September 2025.
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 Kite the way a machine reads it — 6 machine-readable artifacts across 3 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 — Kite scores 40.2/100 (thin), with a separate agent-readiness read of 46/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 Kite
Each block below is one kind of artifact we hold for Kite. 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 3
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.
Kite Chain JSON-RPC (Mainnet)
EVM-compatible JSON-RPC interface for Kite Chain mainnet (chain ID 2366, native token KITE), available over HTTPS and WSS from a global endpoint plus Virginia, Tokyo, and Irelan...
Kite Chain JSON-RPC (Testnet)
EVM-compatible JSON-RPC interface for Kite Chain testnet (chain ID 2368), paired with a public faucet and the testnet Kitescan block explorer for development and integration tes...
Kite Stablecoin Gasless Transfer API
REST relayer that executes stablecoin transfers on behalf of users who hold no native gas token, authorized off-chain with EIP-3009 signed authorizations. GET /supported_tokens ...
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.
kite-mcp.yml
MCP SERVERSecurity 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.
Kite Authentication
passkey/email-otp/oauth2/signed-authorization/delegated-session · 8 schemes
SECURITYResources
Every other property we hold for Kite — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
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/kite · machine-readable index on apis.io