deadends.dev
Registry code: 73ac3db111e3b2b6
Structured error knowledge database for AI coding agents. 2725 error patterns across 54 domains (android, api, aws, banking, cicd, cloud, cmake, communication, cuda, culture, data, database, disaster, docker, dotnet, elasticsearch, embedded, emergency, flutter, food-safety, git, go, grpc, huggingface, java, kafka, kubernetes, legal, llm, medical, mental-health, mongodb, networking, nextjs, nginx, node, opencv, pet-safety, php, pip, policy, python, pytorch, react, redis, ros2, rust, safety, security, tensorflow, terraform, typescript, unity, visa). Query error messages to get dead ends (what…
- endpoint
- https://deadends.dev/
- protocol
- JSONRPC ·0.3
- authentication
- none
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is deadends.dev live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is deadends.dev 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 deadends.dev have?
- 11 tools: Match Error Message, Get Error Details, List Errors By Domain, Batch Lookup, List Errors By Country, List Error Domains, Report Workaround Outcome, Domain Statistics, ….
- Is deadends.dev 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.6%· all time 99.6%
last good check
of 11 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- developer tools
- used for
- match an error message to known fixes
- look up workarounds for an error
- list errors by domain
- report whether a workaround worked
- takes → gives
- text → data
- tools
- 10 reads1 changes data
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.
match-error reads auth-required never probed
Match an error message against 2725 known patterns across 54 domains. Returns dead ends, workarounds with success rates, and error chains.
get-error-detail reads auth-required never probed
Get full structured failure knowledge for a specific error by its ID. Returns complete dead ends, workarounds, transition graphs, and source evidence.
list-by-domain reads auth-required never probed
List all errors in a specific domain with fix rates.
batch-lookup reads auth-required never probed
Look up multiple error messages at once (max 10). Use for debugging error chains or log analysis.
list-errors-by-country reads auth-required never probed
List country-scoped dead ends by ISO alpha-2 code: visa, banking, legal, cultural, medical, food-safety, emergency - jurisdiction knowledge generic LLM training data gets wrong.
list-domains reads auth-required never probed
List all 54 error domains with counts.
report-outcome changes data auth-required never probed
Report whether a workaround worked or failed. Feedback improves fix_success_rate for future agents.
domain-stats reads auth-required never probed
Get quality metrics for a domain: error counts, fix rates, resolvability, confidence levels.
error-chain reads auth-required never probed
Get the transition graph for an error: what errors follow, what precedes it, what gets confused with it.
search-errors reads auth-required never probed
Fuzzy keyword search across all errors. Use when you have a vague description rather than an exact error message.
get-country-summary reads auth-required never probed
Country-level summary: total entries, domain breakdown, average fix rate, latest update. Use to assess coverage before relying on country data.
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 id73ac3db111e3b2b6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/73ac3db111e3b2b6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/73ac3db111e3b2b6?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.