Beta Environment Notice
TDM is currently in Beta. Exercise caution when handling assets. Use at your own risk.
Fast Export
Switch the current page to Markdown for fast agent reading, or download it as a .md file.
TDM is currently in Beta. Exercise caution when handling assets. Use at your own risk.
Fast Export
Switch the current page to Markdown for fast agent reading, or download it as a .md file.
# Payment & Checkout Fallback Summary: When an agent cannot authorize a payment (e.g., empty Gas Tank or missing delegation), the TDM Gateway provides a hosted checkout fallback. This allows the user to manually authorize the payment via a browser wallet. Status: Feature guide Topics: - Checkout fallback mechanics - User-in-the-loop payments - Hosted payment experience - Cross-device payment flows Packages: - tdm-sdk Commands: - tdm make payable
The Hosted Checkout is the bridge between autonomous agent execution and human authorization. It provides a familiar web interface for wallet-based payments when an agent hits a budget limit or a high-value intent.
User opens a checkout link to fund their first Session Gas Tank or AgentVault.
An agent's budget is depleted; the gateway returns a checkout URL to the operator.
Trust policies require manual confirmation for payments over a certain threshold.
Directly sharing a link to a paid resource or skill (e.g., via Obsidian).
The URL contains the resource identifier and an optional session ID to link the payment back to a specific agent's execution context.
If an Intent call fails with a 402 Payment Required status, the response body will include a checkoutUrl.