Handling HTTP 402 from Anakin: The 402 Files #1
Send the provision request unsigned; Anakin returns HTTP 402 with a PAYMENT-REQUIRED x402 v2 challenge. Settle it with an x402 payment client (max amount matching the live catalog), then retry the identical request with PAYMENT-SIGNATURE. Repeating a payment payload is idempotent and never duplicates resources. Provisioning returns the lease plus a one-time at_live_ token.
Frequently asked questions
Which endpoints need x402 payment?
POST /api/v3/resources/persons, POST /api/v3/resources/pages, and renewals. Discovery endpoints are free and public.
Can retrying create two Persons?
No. Payment settles before provisioning and repeating a payment payload is idempotent.
Where does the at_live_ token appear?
Only in the provision or refresh response, in plaintext, exactly once. Store it in secret storage immediately.
Sources: live catalog, resource model, integration guide.