Retry API · Agent infrastructure

A tool call fails.
The work continues.

Make an outbound HTTPS request durable. Schedule backoff, recover interrupted work, and inspect every attempt through one API.

Read the API docs OpenAPI contract

x402 v2 · USDC on Base · Discoverable in Bazaar

RETRY / WORKFLOW

01
Submit the requestPOST retry.exende.dev/v1/retries
02
Recover from failuresExponential backoff · Up to 8 attempts
03
Observe the resultGET /v1/retries/{id}/attempts

Per paid job: $0.02 USDC
Attempts: Up to 8
Lifetime: Up to 24h
History: Per attempt

A focused HTTP workflow

Three steps. One useful primitive.

Submit the request

Create a durable job with the outbound request and an explicit retry policy in one x402-paid call.

POST retry.exende.dev/v1/retries

Recover from failures

Retry schedules transient failures and recovers interrupted work within the job lifetime.

Exponential backoff · Up to 8 attempts

Observe the result

Use a private read token for status and attempt history, or configure an optional signed terminal callback.

GET /v1/retries/{id}/attempts

The request contract

One job.
A documented outcome.

The creation payment covers the job and its permitted outbound attempts. The response includes a private read token for follow-up status and history requests.

Optional terminal callbacks are signed with HMAC and retried independently. The retry policy and target restrictions are documented in the API contract.

Explore the full API reference

bash

Initial request returns HTTP 402 payment requirements

curl -i -X POST \
  https://retry.exende.dev/v1/retries \
  -H "Content-Type: application/json" \
  --data '{
    "request": {
      "method": "GET",
      "url": "https://httpbin.org/status/204"
    },
    "retry": {
      "max_attempts": 8,
      "strategy": "exponential",
      "initial_delay_seconds": 5,
      "max_delay_seconds": 300
    }
  }'

Built for agent workflows

Discover. Pay. Use.

An x402-aware client reads the HTTP 402 payment requirements, settles the exact USDC amount, and retries with its payment signature.

Read the x402 guide Browse infrastructure

Payment model

Paid per created resource.

Jobs Data subscriptions and credits are a separate access model. Infrastructure creation uses its own documented contract and payment requirements.

View Bazaar discovery

A tool call fails.The work continues.