Scroll
Scroll is a native zkEVM Layer 2 for Ethereum, built by Scroll Foundation, that uses zero-knowledge proofs to scale Ethereum while preserving bytecode equivalence with the EVM. Developer surface is dominated by standard Ethereum JSON-RPC endpoints on mainnet and Sepolia testnet, the Scrollscan block explorer (with an Etherscan-compatible REST API), a canonical L1<>L2 bridge with messenger contracts, and a rollup explorer that surfaces batch and proof status. dApp builders use Scroll as a drop-in EVM target with Hardhat, Foundry, viem, ethers, and other standard EVM tooling.
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 Scroll the way a machine reads it — 15 machine-readable artifacts across 9 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 — Scroll scores 34.9/100 (thin), with a separate agent-readiness read of 39/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Scroll
Each block below is one kind of artifact we hold for Scroll. 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 9
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.
Scroll JSON-RPC (Mainnet)
Standard Ethereum JSON-RPC interface for Scroll mainnet (chain ID 534352). Used by wallets, dApps, indexers, and tools to read chain state and submit transactions. Compatible wi...
Scroll JSON-RPC (Sepolia Testnet)
Standard Ethereum JSON-RPC endpoint for Scroll Sepolia testnet (chain ID 534351), used for development, integration testing, and contract deployment dry runs before mainnet.
Scrollscan API
Etherscan-compatible REST API for Scroll mainnet served by Scrollscan - block, transaction, account, token, contract verification, gas, and event log endpoints. Used by analytic...
Scrollscan API (Sepolia)
Etherscan-compatible REST API for the Scroll Sepolia testnet explorer, mirroring the mainnet Scrollscan API surface for development use.
Scroll Rollup Scanner
Web explorer for Scroll rollup batches and proof status - shows L1 batch commit, finalization, and proof submission for each L2 batch. Useful for bridge operators and users trac...
Scroll Native Bridge
Canonical L1 <-> L2 bridge for ETH, ERC-20, and arbitrary messages between Ethereum mainnet and Scroll. Backed by the L1 and L2 Scroll Messenger and Gateway contracts; dApps int...
Scroll Contracts
Solidity contracts that implement the Scroll rollup - L1 / L2 messengers, gateways, ScrollChain commit/finalize logic, and the proving system verifiers. Reference implementation...
Scroll go-ethereum (l2geth)
Scroll's fork of go-ethereum that runs the Scroll zkEVM execution layer and serves the JSON-RPC API. Used by node operators and infrastructure providers running Scroll nodes.
Scroll JSON-RPC API
Ethereum JSON-RPC over HTTP POST
Scroll within the panel for all 9 ·
Open Collections 1
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).
Scroll JSON-RPC
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 six things the Kin Score reads for commercial clarity.
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.
Scroll Zkevm 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.
Scroll Zkevm Finops
FINOPSSecurity 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 Scroll — 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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/scroll-zkevm · machine-readable index on apis.io