Starknet
Starknet is a permissionless Ethereum Layer 2 validity rollup developed by StarkWare, powered by STARK proofs and the Cairo smart contract language. Developers interact with Starknet via a versioned Starknet JSON-RPC (served by Pathfinder, Juno, and Papyrus full nodes as well as Infura / Alchemy / Blast / Nethermind providers), the Cairo toolchain (Scarb, Starknet Foundry, Cairo compiler, cairo-vm), client SDKs (starknet.js, starknet.py, starknet-rs), the StarkGate canonical bridge between Ethereum and Starknet, and Voyager / Starkscan block explorers.
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 Starknet the way a machine reads it — 23 machine-readable artifacts across 1 API, 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 — Starknet scores 34.9/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). 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
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Starknet'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/starknet/"
title="Starknet on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/starknet.svg"
alt="Starknet Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/starknet/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/starknet/"
title="Starknet on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/starknet/card.svg"
alt="Starknet Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Starknet
Each block below is one kind of artifact we hold for Starknet. 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 13
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.
Starknet JSON-RPC Specification
Versioned JSON-RPC specification implemented by Starknet full nodes (Pathfinder, Juno, Papyrus) and infrastructure providers. Defines read methods (starknet_* for blocks, transa...
Starknet Mainnet RPC (Public Providers)
Starknet Mainnet (chain ID SN_MAIN) is reached via the Starknet JSON-RPC at hosted providers — Infura, Alchemy, Blast, Nethermind Voyager, Lava, Chainstack — or via self-hosted ...
Starknet Sepolia RPC (Public Providers)
Public JSON-RPC endpoint for Starknet Sepolia testnet (chain ID SN_SEPOLIA) for development and integration testing.
StarkGate Bridge
Canonical L1<->L2 bridge for ETH and ERC-20 tokens between Ethereum and Starknet, operated by StarkWare. Bridge contracts are open-source.
starknet.js SDK
JavaScript / TypeScript SDK for Starknet — providers, accounts, contract classes, ABI parsing, transaction signing, and integration with browser wallets via the wallet API (get-...
starknet.py SDK
Python SDK for Starknet maintained by Software Mansion, covering account / contract interaction, Cairo ABI handling, and the Starknet JSON-RPC.
starknet-rs SDK
Rust SDK for Starknet with high-performance providers, accounts, contract bindings, ABI codegen, and Cairo serialization.
Cairo Language
Cairo is StarkWare's Turing-complete language for creating provable programs and the canonical smart contract language for Starknet. Distributed as the Cairo compiler (Rust) and...
Pathfinder Full Node
Rust implementation of a Starknet full node from Equilibrium that serves the Starknet JSON-RPC, syncs from Ethereum L1 data, and verifies state transitions.
Juno Full Node
Go implementation of a Starknet full node from Nethermind that serves the Starknet JSON-RPC and acts as a sequencer / RPC backend.
Voyager Block Explorer
Nethermind-built block explorer for Starknet Mainnet and Sepolia with a public REST API for blocks, transactions, contracts, classes, events, and tokens.
Starkscan Block Explorer
Block explorer for Starknet Mainnet, Sepolia, and Sepolia Integration with a public REST API for blocks, transactions, events, classes, and NFTs.
Starknet Starknet JSON RPC API API
The Starknet JSON RPC API API from Starknet — 1 operation(s) for starknet json rpc api.
Scroll within the panel for all 13 ·
Open Collections 3
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).
API Collection
OPEN COLLECTIONStarknet JSON-RPC Starknet JSON RPC API API
OPEN COLLECTIONStarknet JSON-RPC API
OPEN COLLECTIONPricing 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.
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.
Starknet 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.
Starknet Finops
FINOPSEvent 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.
Starknet WebSocket RPC API
AsyncAPI 2.6 description of the Starknet WebSocket JSON-RPC API as defined by the upstream `starknet_ws_api.json` OpenRPC specification (https://github.com/starkware-libs/starkn...
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Starknet API Rules
SPECTRALSecurity Posture 1
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 Starknet — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Company 3
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/starknet · machine-readable index on apis.io
This is an independent, third-party profile of Starknet, 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.