{"uid":"cap_Kk9PVNL_Xgt7lhJ5ouf5l","slug":"retry-after-parse-75bc6b51","name":"Retry After Parse","description":"Retry After Parse: Retry After Parse normalizes Retry-After seconds or an HTTP-date epoch into a delay from bounded caller-supplied values without an external provider. Call Retry After Parse before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for Retry After Parse as versioned deterministic JSON. Price: $0.001 USDC via x402 on Base. First-party, stateless, memory-only…","url":"https://api.delx.ai/api/v1/x402/retry-after-parse","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"value":{"type":"string","maxLength":8192,"description":"Value supplied to Retry After Parse; used only for this bounded calculation and processed in memory without retention."},"now_epoch":{"type":"integer","description":"Now Epoch supplied to Retry After Parse; used only for this bounded calculation and processed in memory without retention."}}},"responseSchema":{"type":"json","example":{"result":{"delay_seconds":120,"retry_at_epoch":1720000120},"schema":"delx/util-retry-after-parse/v1","status":"pass","evidence":{"retained":false,"input_sha256":"d9694253aa50ca3a4c76da4bbf323706780e4a4cfeb723b7ee5a097e2965b646","external_calls":0},"operation":"web_reliability:retry_after_parse"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","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.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_I939eIFYsuB3dGvtuve3g","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Normalizes an HTTP Retry-After header value (seconds or HTTP-date) into a delay in seconds using a caller-supplied current epoch, returning a deterministic pass/advisory finding.","exampleAgentPrompt":"Parse this Retry-After header value — 'Wed, 21 Oct 2025 07:28:00 GMT' — using the current epoch 1745200000 and tell me how many seconds I should wait before retrying.","exampleUseCases":[{"title":"Rate-limited API retry scheduling","prompt":"I just got a 429 response with a Retry-After header saying '120' — my current epoch is 1745200000. Parse that and tell me the delay in seconds and whether it's safe to retry."},{"title":"HTTP-date Retry-After in a crawler","prompt":"My crawler received a Retry-After header with value 'Fri, 01 Aug 2025 12:00:00 GMT' and the current epoch is 1753000000. How many seconds should I wait before making the next request?"},{"title":"Validating Retry-After before caching a redirect","prompt":"Before I cache this redirect response, I need to parse the Retry-After header value 'Thu, 10 Jul 2025 00:00:00 GMT' given now_epoch 1748000000 — is this value valid and what delay does it imply?"}],"resultDescription":"Returns a versioned deterministic JSON object containing the normalized delay in seconds, the raw input evidence, a computed finding, and an explicit pass or advisory status indicating whether the Retry-After value is well-formed and usable.","failureModes":["Missing or empty value field returns an error or advisory status","Invalid date string that cannot be parsed returns an advisory/fail status","now_epoch not supplied or not an integer causes computation failure","Retry-After value exceeds maxLength of 8192 characters is rejected","Negative or zero computed delay may return advisory status"],"whenToPreferThis":"Choose this endpoint when an agent or HTTP client needs to deterministically interpret an HTTP Retry-After header — whether expressed as a seconds integer or an HTTP-date string — into a concrete delay before retrying or caching. It is stateless, requires no API key, and returns structured pass/advisory findings, making it ideal for lightweight client-side rate-limit handling logic inside automated pipelines.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T07:12:44.102Z","isFirstParty":false}