Flashbots
Flashbots is a research and development organization focused on mitigating the negative externalities of Maximal Extractable Value (MEV) on stateful blockchains, starting with Ethereum. Flashbots maintains and operates a set of public infrastructure: the Flashbots Auction JSON-RPC relay for bundle submission, Flashbots Protect RPC for private mempool transactions, the MEV-Share node and protocol for orderflow sharing, MEV-Boost middleware for validators, and SUAVE - an Ethereum-native, MEV-aware, privacy-first encrypted mempool.
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 Flashbots the way a machine reads it — 14 machine-readable artifacts across 7 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 — Flashbots scores 43.3/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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 Flashbots
Each block below is one kind of artifact we hold for Flashbots. 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 7
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.
Flashbots Auction Relay (JSON-RPC)
JSON-RPC endpoint for submitting bundles and private transactions to the Flashbots block builder. Supports eth_sendBundle, eth_callBundle, eth_cancelBundle, eth_sendPrivateTrans...
Flashbots Auction Relay (Sepolia Testnet)
Sepolia testnet instance of the Flashbots Auction JSON-RPC relay for bundle submission and testing without mainnet ETH.
Flashbots Protect RPC
Public-facing Ethereum JSON-RPC endpoint that routes transactions through Flashbots' private mempool to provide frontrunning protection, potential MEV and gas refunds via MEV-Sh...
MEV-Share Node API
Public API for the MEV-Share node, an open-source protocol that lets users, wallets, and apps internalize MEV. Users send private transactions to the node, which selectively sha...
MEV-Boost Relay
Public Flashbots-operated relay used by MEV-Boost middleware. Aggregates blocks from many builders and presents the most profitable one to the proposing validator. Used by valid...
SUAVE
Single Unifying Auction for Value Expression - an Ethereum-native, MEV-aware, privacy-first encrypted mempool and decentralized block building network. Provides a testnet, SDKs,...
Flashbots Flashbots Auction & MEV Share Relay (JSON RPC) API
The Flashbots Auction & MEV Share Relay (JSON RPC) API from Flashbots — 1 operation(s) for flashbots auction & mev share relay (json rpc).
Scroll within the panel for all 7 ·
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).
Flashbots Auction & MEV-Share Relay (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.
Flashbots 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.
Flashbots 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.
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 Flashbots — 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 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 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
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/flashbots · machine-readable index on apis.io