{"uid":"cap_GXIrLvFxfClpjhQPbY9Zt","slug":"delx-api-error-taxonomy-b0f149f5","name":"Delx API Error Taxonomy","description":"Classify an HTTP outcome for retry and remediation without returning its body. Use it as a bounded preflight or analysis step inside an enterprise agent workflow before data, policy, integration, security, or commercial decisions reach production. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, memory-only, and has no paid upstream or input retention. Results are advisory; the caller remains responsible for authoriza…","url":"https://api.delx.ai/api/v1/x402/api-error-taxonomy","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"body":{"type":"string","description":"Input field: body."},"status_code":{"type":"number","description":"Input field: status_code."}}},"responseSchema":{"type":"json","example":{"schema":"delx/util-api-error-taxonomy/v1","category":"upstream_transient","retryable":true,"body_sha256":"93a8ba7fde7cf39ab2dea97fc62f4352331bc174e3c4fbed390d9a8153f4787c","status_code":503,"body_returned":false}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.003","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.003/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_-8CkJnSFo3NUDNLD992iW","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.003","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Classifies an HTTP status code and optional response body into a structured error taxonomy with retry and remediation guidance","exampleAgentPrompt":"Classify HTTP status code 503 with body 'Service temporarily unavailable' — tell me whether to retry and what remediation steps to take.","exampleUseCases":[{"title":"Retry decision in integration pipeline","prompt":"I got a 429 back from a downstream API with body 'Rate limit exceeded, retry after 60s' — classify this error and tell me whether my agent should retry and when."},{"title":"Triage fatal vs transient errors","prompt":"Before my workflow re-queues this failed request, classify status code 502 with an empty body so I know if it's a transient gateway issue or something I need to escalate."},{"title":"Preflight check before commercial decision","prompt":"Classify this HTTP 403 error with body 'Access denied: insufficient permissions' — I need to know the error category and recommended remediation before my agent proceeds with the payment step."}],"resultDescription":"Returns deterministic machine-readable JSON containing the error classification (category, type, severity), whether the error is retryable, recommended retry strategy or backoff guidance, and remediation advice — all derived locally and statelessly from the provided status code and body.","failureModes":["Missing or invalid status_code field returns an error response","Unrecognized or non-standard status codes may yield a generic classification","Very large or malformed body strings may be truncated or rejected","Network issues reaching the endpoint return no taxonomy result"],"whenToPreferThis":"Choose this endpoint when you need deterministic, machine-readable HTTP error classification inside an automated agent workflow — especially for preflight decisions before retrying, escalating, or routing failed API calls. Prefer it over ad-hoc conditional logic when you need structured, consistent taxonomy across many error types without retaining sensitive response payloads.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T18:50:42.228Z","isFirstParty":false}