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, transactions, classes, state, storage, events), trace methods, and write methods for invoking, deploying accounts, and declaring classes.
Starknet JSON-RPC Specification is one of 13 APIs that Starknet publishes on the APIs.io network, described by an AsyncAPI event-driven specification.
Tagged areas include JSON-RPC, Spec, and OpenRPC. The published artifact set on APIs.io includes API documentation and an AsyncAPI specification.
Requests are made against the base URL https://github.com/starkware-libs/starknet-specs.
Metadata
The identity and technical contract details declared by the specification.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Starknet 12
Other APIs Starknet publishes across the network.
This is an independent, third-party profile of Starknet JSON-RPC Specification, 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.