Infrastructure for paid execution across APIs, tools, content, and agent workflows. TDM makes one route, tool, file, or action payable through a programmable settlement layer with optional Session Gas Tank support, vault-scoped controls, and runtime recovery paths.
Install TDM
Put the package and CLI on the machine before anything else.
npm install tdm-sdkThe payment and settlement layer for APIs, agent tools, paid execution, agent vaults, and runtime recovery, with a
single paid execution loop.
Start With One Paid Surface
Use one command in the CLI or one wrapper in code to turn a route, tool, file, or agent step into a paid surface. The settlement and runtime layers take over after that.
CLI
tdm make payableFastest path when you want to price one file, route, URL, or local resource from the CLI.
SDK
makePayable(...)Best when you want the same paid surface idea inside application code, framework wrappers, or custom runtimes.
Paid Surface→Settlement Runtime
Settlement Runtime
Stablecoins move value first. TDM keeps the agent workflow bounded when execution, funding, or delivery gets messy.
Step 01
vault / spend lane
Step 02
rules / authorize
Step 03
paid route / tool
Step 04
retry / MCP / checkout
Product Thesis
TDM is not only about charging an agent. It is about deciding what can run, keeping funds scoped to the right runtime, and giving the workflow a recovery path when the paid sequence breaks mid-flight.
Step One
Step Two
Agent Runtime Guardrails
The agent story is not just “pay and continue.” TDM can scope one agent into its own vault contour, apply trust and spend checks before a paid step runs, and then surface recovery when the workflow depletes, stalls, or needs buyer fallback.
AgentVault
isolate balance, signer posture, and workspace context per agent
Rules
gate execution with trust, limits, and authorization before money is spent
Recovery
hand off to MCP, checkout, refill, or retry when the session is no longer ready
One Runtime Flow
# isolate one agent$ tdm vault create agent-alpha --use # boot it inside the same contour$ tdm agent boot agent-alpha # runtime checks can now decide:# continue, fuel, recover, or hand offAgent Safety Layer
TDM is not only the moment of payment. It is the layer that keeps an agent funded, scoped, checked, and recoverable while real work is running.
Agent-First Capabilities
Vaults, delegated spend, MCP session state, and framework wrappers that keep agent execution controlled after funding
Delegated Spending
import { createSessionTanksClient } from 'tdm-sdk/session-tanks' const tanks = createSessionTanksClient({ baseUrl: process.env.TDM_GATEWAY_URL, rootId: process.env.TDM_ROOT_ID,}) const tank = await tanks.createSubTank({ publicKey: '<agent_public_key>', profile: 'DISCRETE', limitUsd: '5.00'}) const session = await tanks.delegateSession({ tankId: tank.id, sandboxId: '<session_id>', maxSpendUsd: '1.00', ttlSeconds: 3600})Integration Paths
Keep your runtime, keep your language, keep your buyer flow
SDK Surface Area
Vaults, rules, SDK clients, and MCP tools in one place
CLI Commands
connectfuelsweepcashoutagentvaultallowliststorageworkspaceruntimeSDK Clients
authorizegatewaysession-tankscheckoutfetch-hookMCP Tools
tdm_get_session_stateTDM For Obsidian
Obsidian is the quick creator path: connect the CLI once, make the current note payable, and keep paid note flows inside the editor instead of building a separate app first.
Good for premium notes, paid knowledge drops, and creator-only unlock flows.
Ecosystem Reach
External catalogs can surface TDM-backed resources and route buyers into lightweight checkout. When a builder or operator needs vaults, signer access, repeated automation, or deeper runtime control, TDM becomes the native path.
Obsidian
creator notes and paid unlocks
x402 Bazaar
discovery and buy-entry bridge
MPP
service discovery bridge
Start integrating TDM today. Build paid APIs, files, and agents
on one programmable settlement layer.