Safety And Billing
Understand capability prices, payment behavior, availability, and safe retries.
Capability calls use the same Xenodia account, credit, and request history as the rest of the platform. The live descriptor shows the price and supported payment relationships before a call.
Payment Modes
| Mode | Meaning |
|---|---|
owner_only | Charge the owner account. |
self_only | Charge the calling account. |
self_then_owner | Prefer the calling account, then use owner-funded credit when policy allows. |
The response billing object identifies the payer selected for the call and the final amount.
Price Units
Prices use micro USDC. 10000 is 0.01 USDC and 1000000 is 1 USDC. For multi-operation capabilities, read operations[].pricing.unit_price_micro_usdc before each call.
Funds And Failures
| Case | Funds behavior |
|---|---|
| The operation is unavailable before invocation | No funds are locked. |
| An admitted request cannot complete | Any temporary reservation is released or marked for review according to the returned billing status. |
| A successful paid call | The final amount appears in the billing summary. |
| A replay with the same request key and payload | The stored result is returned without charging the same intent twice. |
Safe Retries
Send an Idempotency-Key for paid and asynchronous operations. Reuse the same key only when retrying the same logical request with the same payload. Use a new key for a new user intent. A conflicting payload returns 409 idempotency_conflict.
Availability
| State | Meaning |
|---|---|
active | The operation currently accepts calls. |
unavailable | Xenodia is not accepting new calls for this operation. Follow the public message and retry guidance. |
Availability may change between discovery and invocation. Always handle the invoke response and retain its request_id.
What To Keep
For paid or important calls, retain the request ID, capability slug, operation, version, billing status, final amount, and the input summary needed to explain the request.