Linea
Linea is ConsenSys' ZK-EVM Layer 2 network built on Ethereum, offering low fees, fast finality, and full EVM compatibility. Developers access on-chain data through three complementary API surfaces: a public JSON-RPC endpoint (rpc.linea.build) supporting all standard Ethereum methods plus Linea-specific extensions (linea_estimateGas, linea_getProof), a REST Token API (token-api.linea.build) for ERC-20 token metadata and price history, and the Lineascan block explorer API (Etherscan V2-compatible) for transactions, blocks, addresses, token transfers, event logs, and contract verification across Linea Mainnet (chainId 59144) and Sepolia testnet (chainId 59141).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Linea the way a machine reads it — 37 machine-readable artifacts across 4 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 56.1/100 (developing), 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 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 4
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 JSON-RPC API
Standard Ethereum JSON-RPC API plus Linea-specific extensions available at the public endpoint rpc.linea.build. Supports all eth_* methods (eth_blockNumber, eth_getBlockByNumber...
Linea Explorer API (Lineascan / Blockscout)
Blockchain data APIs for Linea Mainnet backed by two explorer surfaces. The Lineascan (lineascan.build) explorer uses the Etherscan API V2 interface (chain ID 59144) with module...
Linea Prices API
Token price history
Linea Tokens API
ERC-20 token metadata and information
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Linea GraphQL API
The Linea GraphQL API is provided by the Blockscout-based block explorer at `explorer.linea.build`. It exposes blockchain data for Linea Mainnet (chain ID 59144) through a Graph...
GRAPHQLPricing 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.
Linea Plans
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.
Linea 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 Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
EVM-compatible JSON-RPC
Full Ethereum JSON-RPC compatibility means existing Hardhat, Foundry, Truffle, ethers.js, viem, and web3.py tooling works unchanged on Linea.
Linea-specific gas estimation
linea_estimateGas returns baseFeePerGas, priorityFeePerGas, and gasLimit including L1 finalization costs, enabling accurate fee budgeting on the ZK rollup.
ERC-4337 bundler endpoint
Built-in account abstraction bundler methods (eth_sendUserOperation, eth_estimateUserOperationGas, Pimlico extensions) available on the public RPC.
Token REST API
Dedicated REST service at token-api.linea.build for ERC-20 token listings, metadata, security scoring, and 24-hour price history without requiring an API key.
Etherscan-compatible explorer API
Lineascan implements the Etherscan API V2 interface, giving access to all standard explorer modules (accounts, transactions, contracts, tokens, logs, stats) via chain ID 59144.
Dual explorer surfaces
Both Lineascan (Etherscan-style) and a Blockscout instance provide redundant explorer APIs with REST and GraphQL options.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Linea Context
JSON-LDSpectral 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.
Linea API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security 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.
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
DeFi application development
Query token balances, prices, and swap activity to power DEX front-ends, yield dashboards, and portfolio trackers on Linea.
Smart contract deployment and verification
Deploy EVM contracts using standard tooling and verify source code via the Lineascan API for public transparency.
Transaction monitoring
Track address activity, internal transactions, and ERC-20 transfers in real time for wallets, compliance, and analytics.
Gas cost optimization
Use linea_estimateGas to accurately budget L1+L2 costs before submitting transactions, avoiding under-gas failures.
Token analytics
Pull token holder lists, supply data, price history, and security scores to build on-chain analytics and due-diligence tools.
Cross-chain bridge monitoring
Track deposit and withdrawal transactions across the Linea canonical bridge to Ethereum mainnet.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Infura
Managed Linea RPC nodes with private endpoints and higher rate limits via MetaMask developer services.
Alchemy
Alchemy provides Linea RPC nodes with enhanced APIs, webhooks, and developer tooling.
The Graph
Subgraphs can index Linea events for custom GraphQL queries over protocol data.
Dune Analytics
Linea on-chain data is queryable via Dune for SQL-based analytics and dashboards.
Hardhat and Foundry
Standard EVM development frameworks connect to Linea RPC without modification.
Chainlink and Pyth
Price oracles deployed on Linea provide on-chain price feeds for DeFi protocols.
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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/linea · machine-readable index on apis.io