Linea
Linea is an Ethereum zkEVM Layer 2 developed by Consensys, offering full Ethereum equivalence under a zero-knowledge proving system that finalizes state to Ethereum L1. Linea mainnet runs at chain ID 59144 with public JSON-RPC at rpc.linea.build, and a Sepolia testnet at chain ID 59141 at rpc.sepolia.linea.build. Developer surfaces include Linea-specific JSON-RPC extensions (linea_estimateGas, linea_getProof), the Linea SDK, the canonical Linea Bridge, Lineascan block explorer, the Linea POH/attestation system, and a published Linea Stack for deploying Linea-equivalent chains.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Linea the way a machine reads it — 15 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 — Linea scores 29.9/100 (emerging), with a separate agent-readiness read of 7/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 Linea
Each block below is one kind of artifact we hold for Linea. 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.
Linea Mainnet JSON-RPC
Public Ethereum-compatible JSON-RPC endpoint for Linea mainnet (chain ID 59144). Supports the standard eth_* method set plus Linea-specific extensions such as linea_estimateGas ...
Linea Sepolia Testnet JSON-RPC
Public JSON-RPC endpoint for the Linea Sepolia testnet (chain ID 59141), used for application development, prover-changes testing, and bridge integration before deploying to mai...
Linea-Specific JSON-RPC Methods
Linea custom JSON-RPC methods including linea_estimateGas (returns recommended gas limit, base fee, and priority fee accounting for L1 verification costs) and linea_getProof. Do...
Linea SDK
Official TypeScript SDK for interacting with Linea — message-service helpers, bridge claim flows, and L1/L2 utility methods used by app developers and bridge integrators.
Linea Bridge
Canonical Ethereum-Linea bridge for ETH and supported ERC-20 tokens, built on Linea's message service. UI lives at bridge.linea.build.
Lineascan Block Explorer
Etherscan-style block explorer for Linea mainnet — transactions, blocks, contracts, tokens, batches, and Solidity source verification.
Lineascan Sepolia Testnet Explorer
Lineascan instance for the Linea Sepolia testnet, supporting transaction lookup and contract verification for testnet deployments.
Linea Stack
Linea Stack lets infra teams deploy and operate their own Ethereum-equivalent network using the Linea protocol — sequencer, prover, and message-service components.
Linea Proof of Humanity
Linea POH (Proof of Humanity) attestation system used by ecosystem dApps for sybil-resistant identity, queried by contract or via attestation services.
Linea Ecosystem Directory
Public directory of dApps, infrastructure providers, wallets, indexers, and services building on Linea — surfaces partner integrations developers can plug into.
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.
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.
Linea Network 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.
Linea Network Finops
FINOPSSecurity Posture 2
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 Linea — 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 3
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 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
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/linea-network · machine-readable index on apis.io