Starkware

StarkWare Industries builds STARK-proof (Scalable Transparent ARgument of Knowledge) blockchain scaling technology for Ethereum. Its flagship products are Starknet, a permissionless decentralized validity-rollup (ZK-Rollup) where developers deploy Cairo smart contracts, and StarkEx, an application-specific scaling engine for exchanges (spot, perpetual, NFT, and payments). The developer surface centers on the Starknet Node JSON-RPC API (read, write, trace, and WebSocket methods specified in OpenRPC), a Wallet JSON-RPC API, a Proving API, StarkEx REST gateways, first-party SDKs (starknet.js, starknet.py, starkex-js), the starkli CLI, and the Cairo programming language and prover stack (Stwo, Cairo VM). This profile catalogs those machine-readable specs and developer artifacts for the API Evangelist network.

Starkware is listed with 4 APIs on the APIs.io network. Tagged areas include Company, Blockchain, Ethereum, Layer 2, and ZK-Rollup.

The Starkware catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Starkware’s developer surface includes documentation, API reference, getting-started guide, engineering blog, CLI, authentication, changelog, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub

37.7/100 thin ▬ flat Agent 22/100 agent aware Front door AI 1/6 silent library Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0

4 APIs 1 MCP Servers

Company Blockchain Ethereum Layer 2 ZK-Rollup Zero-Knowledge Proofs JSON-RPC CryptographyCairoWeb3 Scaling Starknet

Kin Score

Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0

Composite quality — 37.7/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 12.9 / 17

Access Clarity 0.0 / 17

Operational Transparency 3.8 / 11

Contract Governance 0.5 / 10

Discoverability 6.5 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/starkware: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

JSON RPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Starknet Node JSON-RPC API

The Starknet full-node JSON-RPC API (OpenRPC), covering read methods (blocks, transactions, state, classes, events, fees), write methods (add invoke/declare/deploy-account trans...

Starknet Wallet JSON-RPC API

The Starknet wallet JSON-RPC API (SNIP-based) that dApps use to talk to browser/extension wallets: request accounts, permissions, chain switching, typed-data signing, and submit...

Starknet Proving API

The Starknet proving JSON-RPC API for submitting transactions to be proven by the STARK prover.

StarkEx REST API

StarkEx application-specific scaling engine REST API for spot and perpetual trading systems, exposing Gateway, Feeder Gateway, and Availability Gateway endpoints plus documented...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Starkware MCP Server

Official StarkWare MCP (Model Context Protocol) server that exposes all Starknet JSON-RPC v0.10.2+ read and trace methods as agent tools, letting an assistant read blocks, trans...

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Starkware Websocket Events

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Starkware Authentication

none/api-key-at-provider · 3 schemes

SECURITY

Starkware Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Deprecation

Deprecation

ChangeLog

ChangeLog

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Protobuf

Protobuf

Source (apis.yml)

aid: starkware
name: Starkware
description: StarkWare Industries builds STARK-proof (Scalable Transparent ARgument of Knowledge) blockchain scaling technology
  for Ethereum. Its flagship products are Starknet, a permissionless decentralized validity-rollup (ZK-Rollup) where developers
  deploy Cairo smart contracts, and StarkEx, an application-specific scaling engine for exchanges (spot, perpetual, NFT, and
  payments). The developer surface centers on the Starknet Node JSON-RPC API (read, write, trace, and WebSocket methods specified
  in OpenRPC), a Wallet JSON-RPC API, a Proving API, StarkEx REST gateways, first-party SDKs (starknet.js, starknet.py, starkex-js),
  the starkli CLI, and the Cairo programming language and prover stack (Stwo, Cairo VM). This profile catalogs those machine-readable
  specs and developer artifacts for the API Evangelist network.
url: https://raw.githubusercontent.com/api-evangelist/starkware/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- dcvc
- multicoin-capital
- pantera-capital
- paradigm
- wing-venture-capital
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
image: https://github.com/starkware-libs.png
tags:
- Company
- Blockchain
- Ethereum
- Layer 2
- ZK-Rollup
- Zero-Knowledge Proofs
- JSON-RPC
- Cryptography
- Cairo
- Web3
- Scaling
- Starknet
apis:
- name: Starknet Node JSON-RPC API
  description: The Starknet full-node JSON-RPC API (OpenRPC), covering read methods (blocks, transactions, state, classes,
    events, fees), write methods (add invoke/declare/deploy-account transactions), trace methods, and a WebSocket subscription
    API for new heads, events, and transaction status. Spec version 0.10.4-rc.0.
  humanURL: https://docs.starknet.io/
  baseURL: https://docs.starknet.io/
  properties:
  - type: OpenRPC
    name: Starknet Read API (OpenRPC)
    url: openrpc/starkware-starknet_api_openrpc.json
  - type: OpenRPC
    name: Starknet Write API (OpenRPC)
    url: openrpc/starkware-starknet_write_api.json
  - type: OpenRPC
    name: Starknet Trace API (OpenRPC)
    url: openrpc/starkware-starknet_trace_api_openrpc.json
  - type: OpenRPC
    name: Starknet WebSocket API (OpenRPC)
    url: openrpc/starkware-starknet_ws_api.json
  - type: OpenRPC
    name: Starknet Executables API (OpenRPC)
    url: openrpc/starkware-starknet_executables.json
  - type: OpenRPC
    name: Starknet Metadata API (OpenRPC)
    url: openrpc/starkware-starknet_metadata.json
- name: Starknet Wallet JSON-RPC API
  description: 'The Starknet wallet JSON-RPC API (SNIP-based) that dApps use to talk to browser/extension wallets: request
    accounts, permissions, chain switching, typed-data signing, and submitting invoke/declare transactions.'
  humanURL: https://docs.starknet.io/
  baseURL: https://docs.starknet.io/
  properties:
  - type: OpenRPC
    name: Starknet Wallet API (OpenRPC)
    url: openrpc/starkware-wallet_rpc.json
- name: Starknet Proving API
  description: The Starknet proving JSON-RPC API for submitting transactions to be proven by the STARK prover.
  humanURL: https://docs.starknet.io/
  baseURL: https://docs.starknet.io/
  properties:
  - type: OpenRPC
    name: Starknet Proving API (OpenRPC)
    url: openrpc/starkware-starknet_proving_api_openrpc.json
- name: StarkEx REST API
  description: StarkEx application-specific scaling engine REST API for spot and perpetual trading systems, exposing Gateway,
    Feeder Gateway, and Availability Gateway endpoints plus documented error codes.
  humanURL: http://docs.starkware.co/starkex/index.html
  baseURL: http://docs.starkware.co/starkex/index.html
common:
- type: Website
  url: https://starkware.co
- type: DeveloperPortal
  url: https://docs.starknet.io/
- type: Documentation
  url: https://docs.starknet.io/
- type: APIReference
  url: https://github.com/starkware-libs/starknet-specs
- type: GettingStarted
  url: https://www.starknet.io/developers/
- type: Blog
  url: https://starkware.co/blog/
- type: GitHubOrganization
  url: https://github.com/starkware-libs
- type: Protobuf
  name: Starknet P2P protocol buffers
  url: grpc/_index.yml
- type: Packages
  url: packages/starkware-packages.yml
- type: SDKs
  url: packages/starkware-packages.yml
- type: CLI
  url: cli/starkware-cli.yml
- type: MCPServer
  url: mcp/starkware-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/starkware-authentication.yml
- type: Conventions
  url: conventions/starkware-conventions.yml
- type: ErrorCatalog
  url: errors/starkware-problem-types.yml
- type: Lifecycle
  url: lifecycle/starkware-lifecycle.yml
- type: Deprecation
  url: lifecycle/starkware-lifecycle.yml
- type: ChangeLog
  url: changelog/starkware-changelog.yml
- type: Conformance
  url: conformance/starkware-conformance.yml
- type: DataModel
  url: data-model/starkware-data-model.yml
- type: Webhooks
  url: asyncapi/starkware-websocket-events.yml
- type: Sandbox
  url: sandbox/starkware-sandbox.yml
- type: DomainSecurity
  url: security/starkware-domain-security.yml
- type: LLMsTxt
  url: llms/starkware-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 43
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/starkware"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/starkware/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/starkware/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.