BlockRun API
Registry code: 046b7c941167cfec
BlockRun is the routing and payment layer for AI. One OpenAI-compatible endpoint routes to 100+ LLMs plus image, video, music and speech generation, web search, prediction-market and on-chain data, and multi-chain RPC. This host is the account-balance entry point: authenticate with an API key and pay from a BlockRun account funded by card or wire — no wallet signature per call. The same services are also sold per call in USDC over x402 at blockrun.ai (Base), sol.blockrun.ai (Solana) and arc.blockrun.ai (Arc).
- endpoint
- https://api.blockrun.ai/v1
- protocol
- JSONRPC ·0.3
- authentication
- http
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is BlockRun API live?
- Yes — it answered the hub's last check (checked 43m ago). It answered 99% of checks over the last 30 days.
- Is BlockRun API free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does BlockRun API have?
- 5 tools: Web search, Account-balance billing, Image, video, speech, Chat & LLM routing, Decisions for agents.
- Is BlockRun API safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- route chat requests across many llms
- generate images video or speech
- search the web news and x
- get yes or no judgments over text
- takes → gives
- text → text, images, video, audio, data
- tools
- 5 reads
- note
- resells another provider
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search reads auth-required never probed
Live web, news and X search.
account reads auth-required never probed
API key + prepaid balance (card or wire); exact-usage metering; /v1/usage is the record.
media reads auth-required never probed
Image, video and speech generation; account-owned image request history at GET /v1/images with cursor pagination and authenticated result downloads.
chat reads auth-required never probed
OpenAI-, Anthropic- and Responses-compatible chat across frontier and open-weight models.
judgment reads auth-required never probed
Yes/no, choice and score judgments over text or images, with probabilities: POST /v1/decisions, OpenAI Decisions API compatible (gpt-6-luna). Billed from credit per input token at the gpt-6-luna input price plus account margin.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your agent card — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id046b7c941167cfec.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/046b7c941167cfec/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/046b7c941167cfec?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.
Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- blockrun.ai BlockRun