Paid summary retry matrix
Successful free search and publication-discovery requests also return
200,
but they are not charged.
Error bodies
Invalid search parameters return400 with field-level details:
401:
403:
404:
503:
Safe retry patterns
Free discovery requests
ForGET /api/v1/search and publication discovery routes, retry transient 500
responses with exponential backoff and jitter. Do not retry 400 or 404
responses without changing the request.
Summary not ready
For503 summary_not_ready, wait before retrying. The response does not include
a payment challenge, so no payment was attempted.
Wallet payments
The normal wallet flow contains exactly one expected retry:- Send a plain request and receive
402. - Inspect and approve the challenge.
- Retry through the x402 or MPP-aware client.
- Store the successful response.
502, inspect the wallet transaction or MPP
receipt before making another paid request.
API-key payments
An API-key request checks available credits before debiting them. A401 or
403 is safe to correct and retry. If the request times out after being sent,
check account credit activity before repeating it because the debit and response
may already have completed.

