Back to Browse
Delx Retry Safe Classify
x402
Delx Retry Safe Classify is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).
Classifies whether a failed HTTP-style call is safe to automatically retry, returning a deterministic machine-readable JSON verdict.
Price / call$0.001
Success—
StatusUnknown
How this service works
Classify whether a failed HTTP-style call is safe to auto-retry — first-party local utility for agent preflight and proven micro-utils expansion. Returns deterministic machine-readable JSON for $0.001 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, no web search, no live RPC, and no mediagen. Results are advisory; the caller owns authorization, budgets, and production controls. Sibling of Delx routes that already…
Output
A deterministic JSON object indicating whether the given HTTP call is safe to auto-retry, based on the method, status code, body mutation behavior, and idempotency key presence. No state is stored; results are advisory and stateless.
Example use cases
Agent preflight before retrying failed webhook
“I have a failed POST webhook call that returned a 500 status — the body mutates data and there's no idempotency key. Should my agent automatically retry it or is that unsafe?”
Retry safety check for idempotent PUT
“My pipeline got a 429 on a PUT request. The body doesn't mutate state and I do have an idempotency key set — can you classify whether it's safe to retry automatically?”
Resilience policy guard for GET timeouts
“A GET request in my workflow timed out with a 504 — body doesn't mutate anything and there's no idempotency key. Is it safe to have my agent retry this automatically?”
Technical details
Endpoint
POSThttps://api.delx.ai/api/v1/x402/retry-safe-classifyWhen to prefer
Use this endpoint when an AI agent or orchestration layer needs a deterministic, rule-based advisory on retry safety before re-issuing a failed HTTP call — especially in automated pipelines where incorrect retries could cause duplicate mutations, financial side effects, or data corruption. Prefer this over hand-coded retry logic when you want a consistent, auditable classification step at near-zero cost ($0.001 USDC) that is stateless and has no upstream dependencies.
Side effects
- Missing required fields (method or status_code) may return a validation error
- Invalid method string or non-integer status code causes malformed input rejection
- Ambiguous combinations (e.g. POST with no body_mutates flag) may return conservative non-retry verdict
- Payment failure over x402 results in 402 response before classification occurs
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| method | string | Input field: method. |
| status_code | integer | Input field: status code. |
| body_mutates | boolean | Input field: body mutates. |
| idempotency_key_present | boolean | Input field: idempotency key present. |
Output
Schema · Response
{
"type": "json",
"example": {
"advice": "retry_with_backoff",
"method": "POST",
"reason": "transient_status_with_idempotency_key",
"schema": "delx/util-retry-safe-classify/v1",
"retry_safe": true,
"status_code": 503
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"