Match an error message against deadends.dev's database of known errors. Returns dead ends (what NOT to try), workarounds (what works), and error chains (what comes next). Use this BEFORE attempting to fix any error to avoid wasting time on approaches that are known to fail. Covers 51 domains including python, node, docker, git, cuda, typescript, rust, go, kubernetes, terraform, aws, react, java, database, pytorch, tensorflow, and 34 more. Use list_error_domains to see all.

Get full details for a specific error by its ID (e.g., 'python/modulenotfounderror/py311-linux'). Includes all dead ends, workarounds, error chain info, and source evidence.

List all error domains and counts in the deadends.dev database. Covers 51 domains including programming languages, frameworks, infrastructure, ML/AI, culture, safety, medical, legal, and more.

Search errors by keyword across all domains. Unlike lookup_error (which uses regex matching), this does fuzzy keyword search. Use when you have a vague description like 'memory issues' or 'permission denied' rather than an exact error message.

List all errors in a specific domain with their fix rates. Use this to understand coverage for a domain before relying on it.

Look up multiple error messages at once. Returns the best match for each error. Use when debugging a chain of errors or analyzing a log with multiple failures.

Get detailed statistics for a domain: error counts, average fix rate, resolvability breakdown, top categories, and confidence levels. Use this to assess how trustworthy deadends.dev data is for a domain.

List all country-scoped dead ends for a given country (ISO alpha-2 code, e.g. 'kr', 'jp', 'us', 'de'). Returns visa, banking, legal, cultural, medical, food-safety, emergency, and safety dead ends specific to that jurisdiction. Use this when an AI agent needs jurisdiction-specific knowledge that global LLM training data won't reliably cover.

Get a country-level summary: total entries, domain breakdown, average fix rate, and most-recent updates for the country. Use this to assess coverage for a country before relying on deadends.dev for trip / business / legal planning advice.

Traverse the error transition graph for a specific error. Shows what errors typically follow this one (leads_to), what errors usually precede it (preceded_by), and what errors are frequently confused with it. Use this to diagnose cascading failures and predict what comes next.

Report whether a workaround from deadends.dev worked or failed. This feedback improves fix_success_rate and confidence for future users. Call this AFTER applying a workaround to help improve the database. Accepts the error ID, the workaround action you tried, and whether it succeeded.