Mantle Network
Mantle is a high-performance, EVM-compatible Ethereum Layer 2 network with a modular architecture that combines an optimistic rollup execution layer with EigenDA for data availability. The ecosystem also includes Mantle Liquid Staking Protocol (mETH) and Mantle Restaked ETH. Developer surface is built on standard Ethereum JSON-RPC endpoints (mainnet and Mantle Sepolia testnet), WebSocket subscriptions, the Mantle Explorer (Blockscout-based REST API), a canonical L1 <-> L2 bridge, and standard EVM SDKs (viem, ethers, Hardhat, Foundry, Thirdweb).
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 Mantle Network the way a machine reads it — 14 machine-readable artifacts across 8 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 — Mantle Network scores 33.3/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.
How we profile Mantle Network
Each block below is one kind of artifact we hold for Mantle Network. 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 8
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.
Mantle JSON-RPC (Mainnet)
Standard Ethereum JSON-RPC endpoint for Mantle mainnet (chain ID 5000). Used by wallets, dApps, indexers, and tooling to read chain state and submit transactions on the Mantle L2.
Mantle WebSocket (Mainnet)
WebSocket endpoint for real-time JSON-RPC subscriptions on Mantle mainnet - new blocks, new pending transactions, and log subscriptions.
Mantle JSON-RPC (Sepolia Testnet)
Standard Ethereum JSON-RPC endpoint for the Mantle Sepolia testnet, used for development, contract deployment dry runs, and integration testing.
Mantle Explorer API
Blockscout-based REST API behind explorer.mantle.xyz - blocks, transactions, addresses, tokens, smart-contract verification, and event log endpoints. Used by analytics dashboard...
Mantle Bridge
Canonical L1 <-> L2 bridge for ETH, MNT, ERC-20, and ERC-721 assets between Ethereum mainnet and Mantle. dApps integrate via the published Standard Bridge contracts and the Mant...
Mantle SDK
TypeScript SDK for bridging MNT, ETH, ERC-20, and ERC-721 tokens between Ethereum L1 and Mantle L2. Mirrors the Optimism SDK shape and wraps the Standard Bridge contracts.
Mantle Liquid Staking Protocol (mETH)
Mantle LSP issues mETH, a liquid staking token backed by ETH staked to Ethereum validators. Smart contracts on Ethereum L1 expose stake, unstake, and accounting functions; dApps...
Mantle OP Stack Fork
Mantle's node software, forked from Optimism's OP Stack and modified to use EigenDA for data availability and a token-gas MNT model. Source for op-node, op-batcher, op-proposer,...
Scroll within the panel for all 8 ·
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.
Mantle 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.
Mantle Network 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.
Mantle Network WebSocket JSON-RPC
AsyncAPI description of the Mantle Network WebSocket JSON-RPC interface. Mantle is an EVM-compatible Ethereum Layer 2 built on a modified OP Stack with EigenDA for data availabi...
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.
Mantle Network 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 Mantle Network — 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
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 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mantle-network · machine-readable index on apis.io