intent_get
Returns the current lifecycle state of a registered Intent and the orders (units of fulfilment) under it. WHEN TO CALL: - To check whether a deferred or multi-merchant fulfilment has completed, and which of its orders succeeded - Before starting another order under the same Intent, to see what is left - After the fact, for reconciliation or dispute support Input: intent_id to read one Intent; omit it to list your Intents, with optional status filter and limit Output: intent_id, intent_status, orders[] with per-order status and type (CONDITIONAL until the payment closes, then FINAL), and a state block projecting cumulative spend and occurrence count intent_status is DERIVED from the orders: COMPLETED when all succeeded, COMPLETED_WITH_EXCEPTIONS on mixed outcomes, PARTIALLY_COMPLETED while some are still open. The credential chain is not returned — only references to it. Only Intents registered by the calling agent are visible, and an empty result does not distinguish absent from not-yours.
Input Schema
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"description": "Max Intents to list (default 20, max 100)"
},
"status": {
"type": "string",
"description": "Filter the listing by status: [COMPLETED, SUSPENDED, FAILED, REVOKED, REGISTERED, APPROVED, COMPLETED_WITH_EXCEPTIONS, PARTIALLY_COMPLETED]"
},
"intent_id": {
"type": "string",
"description": "Read a single Intent by its stable reference"
}
}
}Stores exposing the intent_get tool
Get the agentic commerce digest every Monday
Real adoption data, ecosystem trends, new spec versions, and the stores that broke or recovered this week. Read by founders and engineers building the next generation of commerce.