01
Economic context
Requests describe the participant, purpose, asset, recipient, and intended action, not only an amount.
Appearance
Runtime APIs
Create intents, execute approved payments, verify receipts, and inspect Runtime outcomes through structured interfaces.
Explore the intended API architecture without relying on fabricated live responses.
API explorer
Move through the intended endpoints and compare request and response structures from one workspace.
/v1/intentsDescribe the actor, recipient, asset, amount, purpose, and requested economic action.
{
"type": "agent-payment",
"actor": {
"type": "ai-agent",
"id": "configured-agent"
},
"recipient": {
"id": "approved-recipient"
},
"amount": {
"asset": "USDC",
"value": "<amount>"
},
"purpose": "Approved digital resource"
}Interface preview
Endpoint paths and payloads shown here represent the intended public API design. They are not a production API guarantee.
01
Requests describe the participant, purpose, asset, recipient, and intended action, not only an amount.
02
Applications receive explicit Runtime outcomes that can be inspected and handled consistently.
03
Settlement results can produce deterministic receipts rather than disappearing behind a generic success state.
Developer path
Walk through the same Runtime lifecycle through the SDK workspace.