Skip to main content
The crypto rail is a single action. The agent supplies a URL, an idempotency key, and the budget to draw on; Anchorage Agentic Banking does the rest. For the full under-the-hood flow, approvals, and failure modes, see Crypto payments.

​
What the agent provides

  • The URL to fetch.
  • An idempotency key, unique per intent.
  • The budget to draw on (budget_id).
  • Optional: HTTP method, headers, body. Defaults to GET with no body.

​
Estimating cost first

If the agent wants to know what a URL will cost before drawing on the budget, it can pre-flight the URL to get the price back — without committing any spend.

​
Retry cheat sheet

The full table lives in Crypto payments → Failure modes. At a glance:
  • Over the budget cap → poll for the approval verdict, then re-issue with the same idempotency key.
  • Compliance failure (merchant inactive / not on allowlist) → switch merchants.
  • Schema mismatch → fix the request body, retry with a new idempotency key.
  • Upstream 5xx → retry with the same idempotency key — repeat calls collapse to one settlement.
  • Daily safety cap reached → hard reject, no approval path — see Crypto payments → Failure modes.