TDM AgentPay

Use this skill for

HTTP 402 responses from POST /authorize
billingMode, settlementMode, paymentOptions, and retryEndpoint
current JS helper names such as createAuthorizeClient(...), createGatewayClients(...), createSessionTanksClient(...), and createCheckoutClient(...)
session recovery using tdm_get_session_state
session_gas_tank guidance
sweep vs cashout clarification
agent vault command guidance
agent-first paid execution guidance for tools, APIs, routes, and runtime actions

Do not invent undocumented payment fields.
Prefer exact current fields: allowed, authorizationId, charged, balanceMinor, priceMinor, billingMode, settlementMode, paymentOptions, and retryEndpoint.
Use tdm_get_session_state before asking the user for money.
If the state is UNINITIALIZED, instruct the user to run tdm connect.
If the state is DEPLETED and dust is available, prefer tdm sweep.
If the state is DEPLETED and no dust is available, suggest tdm fuel.
Do not describe tdm sweep as a cashout.
Do not suggest tdm cashout as a way to satisfy an active payment challenge.

tdm vault create <name> [--use]
tdm vault use <name|default>
tdm connect
tdm login --gateway https://tdm.todealmarket.com (advanced/manual only)
tdm fuel --amount <usd> --yes
tdm sweep --network solana --resume-burner --deposit-address <solana_address>
tdm sweep --network solana --resume-burner --target-agent <name>
tdm sweep --network base --project-id <walletconnect_project_id> --treasury <base_address>
tdm sweep status
tdm cashout
tdm agent list
tdm agent boot <name>

Prefer one named vault per business contour when operators manage many agents.
For larger fleets, prefer multiple named vaults over one giant vault.
If the operator uses named vaults, respect their active vault or explicit --vault <name> choice.

Treat TDM as agent-first and API-first.
Default mental model: price a protected call, authorize it, then continue execution.
Mention file, note, or content unlock flows only as an additional layer on top of the core agent/runtime payment surface.