zkSync
zkSync is a family of Ethereum Layer 2 scaling networks from Matter Labs built on zero-knowledge proofs. zkSync Era is the production zkEVM rollup; the ZK Stack is the open-source framework used to deploy ZK Chains that interoperate in the Elastic Network. Developers integrate via standard JSON-RPC (with zkSync-specific extensions for paymasters, account abstraction, and L1<->L2 messaging), the zksync-ethers / zksync2-* SDKs, hardhat-zksync and foundry-zksync toolchains, the canonical Bridge, and Blockscout-based 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 zkSync the way a machine reads it — 16 machine-readable artifacts across 10 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 — zkSync scores 36.0/100 (thin), with a separate agent-readiness read of 13/100 (human only). 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 zkSync
Each block below is one kind of artifact we hold for zkSync. 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 10
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.
zkSync Era Mainnet JSON-RPC
JSON-RPC endpoint for zkSync Era mainnet (chain ID 324). Implements standard eth_* methods plus zks_* extensions for L1 batch info, fee estimation, bridge contracts, paymaster p...
zkSync Era Sepolia JSON-RPC
JSON-RPC endpoint for the zkSync Era Sepolia testnet (chain ID 300) used for development, contract deployment, and integration testing.
zkSync Era WebSocket
WebSocket variant of the zkSync Era JSON-RPC endpoint for real-time eth_* subscriptions (newHeads, logs, pendingTransactions) and zks_* subscriptions.
zksync-ethers SDK
TypeScript SDK built on top of ethers.js that adds zkSync-specific providers, signers, paymaster helpers, account-abstraction utilities, deposit and withdrawal flows, and contra...
zksync2-go SDK
Official Go SDK for zkSync Era with support for transactions, EIP-712 typed data, paymasters, deposits, and withdrawals.
hardhat-zksync
Suite of Hardhat plugins for zkSync development — compile, deploy, verify, run local nodes, upgrade contracts, and integrate with the zkVM toolchain.
foundry-zksync
Fork of Foundry (forge / cast / anvil) with first-class zkSync support for compiling, testing, scripting, and deploying contracts to zkSync Era and ZK-Stack chains.
zkSync Era Bridge
Canonical cross-chain bridge between Ethereum L1 and zkSync Era for ETH and ERC-20 tokens. The Portal also exposes bridging across ZK Chains in the Elastic Network.
ZK Stack
Open-source framework (zksync-era + era-contracts) for deploying customizable ZK Chains that share liquidity and security through the Elastic Network shared bridge.
zkSync Era Block Explorer API
Official Blockscout-based block explorer for zkSync Era with REST API exposing blocks, batches, transactions, addresses, contracts, and token data.
Scroll within the panel for all 10 ·
Pricing 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.
Zksync Plans Pricing
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.
Zksync 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.
Zksync 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.
zkSync Era WebSocket JSON-RPC PubSub API
AsyncAPI description for the zkSync Era WebSocket JSON-RPC PubSub endpoint. zkSync Era is fully compatible with Geth's pubsub API, except for the `syncing` subscription. Clients...
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.
zkSync 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.
Resources
Every other property we hold for zkSync — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 4
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/zksync · machine-readable index on apis.io