This page describes intended capability and integration boundaries so people and agents can prepare safely. Do not send this request or register it as an executable tool. Wait until the capability registry marks it implemented-contract, then re-fetch the deployed OpenAPI document and build the request from that machine contract.
PURPOSE + BUSINESS CONTEXT
Planned capability: cancel an eligible pending intent and release its reserved budget without signing or broadcasting.
WHEN THIS CALL IS USEFUL
Do not call or register this operation as an executable agent tool yet. Use this page to plan the future intent workflow; enable it only after the status becomes implemented-contract and the exact operation appears in deployed OpenAPI.
OUTCOME · Planned · Create or advance
What changes
None today: this route is not executable. Its intended behavior is: creates or advances only the intent resource described by this contract after authorization, validation, policy, and idempotency gates pass.
WHY IT MATTERS
Lets people and agents prepare for intent without falsely presenting roadmap scope as a live capability.
Gives people and agents a contract-backed way to advance intent.
Makes custody state understandable without exposing seeds, shares, nonces, private keys, or other reusable signing material.
ISOLATION + AUTHORITY
The authenticated owner, workspace, network, and wallet policy remain authoritative. A wallet record, policy result, approval, ceremony, or balance never grants another lifecycle stage and cannot substitute for threshold signing or separately owned funding, settlement, publisher, matching, or trading authority. This planning record grants no runtime authority, and only deployed OpenAPI can define an executable public contract.
BEFORE YOU CALL
First confirm that this operation is marked implemented-contract and exists in the currently deployed OpenAPI document; until then, no production request is valid.
Its capability-registry profile is provisional integration guidance, not an executable request schema.
Authenticate at the documented boundary: bearer+scope.
Treat the proposed binding_id (path), intent_id (path) as planning input only; re-generate the request from deployed OpenAPI before making a call.
Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
Resolve the active workspace, network, wallet lifecycle, and applicable custody policy before relying on this result.
WHAT TO DO NEXT
Keep this operation disabled in clients, agents, SDKs, and workflow automation while it remains planned-contract.
Use the stated owner, lifecycle, authority boundary, and provisional intent profile to prepare requirements and conformance tests without sending a request.
Monitor the capability registry for implemented-contract, then re-fetch deployed OpenAPI and validate its exact security, parameters, schemas, responses, and agent metadata before enabling the integration.
AGENT GUIDANCE
Never call this planned contract, include it in an executable tool registry, or infer runtime availability from this readable page.
Its capability-registry profile is provisional integration guidance, not an executable request schema.
Use intent only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Treat the proposed binding_id (path), intent_id (path) as planning input only; re-generate the request from deployed OpenAPI before making a call.
Keep enrollment, activation, policy evaluation, approval, ceremony, signing, submission, confirmation, and settlement as distinct states.
After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.
When implementation lands, discard generated requests based on this planning record and rebuild them from the deployed OpenAPI operation.
AI WALLET AUTHORITY BOUNDARY
Implemented reads expose bearer-derived workspace projections, exact policy versions and commitments, independent native-asset budgets, retained decisions, and execution-readiness evidence. POLICY_APPROVED is not transaction construction, signing, broadcast, confirmation, or settlement. The implemented intent-evaluation route is a dry run: it creates no intent, reservation, event, approval, transaction, signature, or broadcast. Any lifecycle, policy, retained-intent, cancellation, or execution operation marked planned is non-executable and must not be registered as an agent tool.
MACHINE CONTRACT
This operation is a non-executable planning contract. Its capability-registry record defines the intended owner, parameters, responses, and integration boundary until an implemented Rust OpenAPI operation replaces it.
EXTENDED INTEGRATION GUIDANCE
Readable request and response reference
Examples describe the reviewed planning contract and remain non-executable until promoted into OpenAPI.
ASCII string · 1–128Caller-generated stable key reused for retries of the same logical mutation.EXAMPLEpost-api-v2-ai-wallets-binding-id-intents-intent-id-cancel-request-001
string · max 500Audit rationale for cancellation.EXAMPLEreason-01
REQUEST
JSON body example
{
"reason": "reason-01"
}
RESPONSES
Status and payload examples
200Mutation accepted and canonical state returned.Not executable · JSON RESPONSE+
{
"result": "See the operation's authoritative OpenAPI response schema."
}
INTEGRATION DECISION
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
401Bearer credential is missing, expired, or invalid.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "Bearer credential is missing, expired, or invalid."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
403The principal lacks the required scope, role, tenant, or step-up authority.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "The principal lacks the required scope, role, tenant, or step-up authority."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
400The request or required headers are malformed.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "The request or required headers are malformed."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
404The resource does not exist in the authenticated workspace.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "The resource does not exist in the authenticated workspace."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
409The request conflicts with wallet or binding state, policy version, or a prior idempotent operation.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "The request conflicts with wallet or binding state, policy version, or a prior idempotent operation."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
422Path, query, or body validation failed.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "Path, query, or body validation failed."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
503The authoritative service or read model is unavailable.Not executable · JSON RESPONSE+
{
"code": "request_failed",
"message": "The authoritative service or read model is unavailable."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts through an implemented operation.
ESCALATE WHEN
Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.
OPERATIONAL NOTES
Security and lifecycle guarantees
The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
Mutations are retry-safe only when the same Idempotency-Key and canonical request body are reused.
The gateway derives profile and workspace context from the authenticated principal; clients cannot supply or override either boundary.
Policy evaluation is fail-closed. An accepted intent is a reserved authorization record, never a signature or broadcast transaction.
Private key material, MPC shares, seeds, signing nonces, and participant secrets are never accepted or returned.
DOCUMENTATION STATUS
This planned contract now defines its public parameters, authorization boundary, replay behavior, responses, and authoritative owner. It remains non-executable until its owner adapter and conformance tests are promoted into the Rust gateway.