TDM Protocol: Settlement for the Invisible Economy
Infrastructure for humans, businesses, and agents. TDM makes APIs, files, content, and agent workflows payable through a programmable settlement layer with optional Session Gas Tank support.
Beta Active
TDMMAKEITPAYABLE
Install TDM
Put the package and CLI on the machine before anything else.
$
npm install tdm-sdkRecommended for all platforms
The payment layer for APIs, agent tools, paid execution, and optional content unlock, with a
frictionless settlement experience.
Command Surfaceremember the command, not just the slogan
CLI
$
tdm make payableRegister routes, tools, URLs, and optional paid content through one memorable command.
SDK
{ }
makePayable(...)Same idea in code when you want route wrappers instead of a terminal flow.
Use the command forCONTENT
Start Here
Simple Paths For Real People
You do not need to learn the whole stack first. Connect once, pick the path that matches your goal, and start accepting or using stablecoins.
Receive Payments
Price Routes, Tools, Or Content
- 1Install tdm-sdk
- 2Run tdm connect once
- 3Use tdm make payable with a price
Good when you want the fastest path from a route, tool call, or paid resource to live charging.
Pay Quickly
Use Stablecoins Without Repeating Setup
- 1Install tdm-sdk
- 2Run tdm connect once
- 3Top up with tdm fuel
Good when you want paid calls to keep flowing after one simple setup.
Recover Or Withdraw
Sweep Leftovers Or Cash Out
- 1Use tdm sweep for local recovery
- 2Use tdm cashout to send stables out
- 3Keep the same connected wallet
Good when you want to clean up dust or send stablecoins back to your wallet.
V0.0.1-BETA
$tdm connect
[✔]Wallet linked. Payment setup ready.
$tdm make payable ./agent-route.ts --price 0.05
[✔]Price locked. Ready to accept stablecoin payments.
_
Ecosystem Reach
Discover Anywhere. Go Deeper With TDM.
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
Choose Your Integration Path
JS SDK, Protocol-First, or MCP-Assisted
Start with the surface that matches your runtime. The core experience stays the same: paid access, optional Session Gas Tank, and seller payout support across the stack.
JS SDK
Framework-Mode
Use tdm-sdk for Next.js, Hono, Express, Elysia, and other JS runtimes with payable wrappers, route guards, and smart CLI flows.
Best when you want to wrap a route or tool inside code with makePayable(...).
Open SDK Docs
Protocol-First
Any Language
Integrate from Python, Go, Java, Rust, C, or C++ through the public TDM contract and ship without waiting for a native SDK.
Best when you already have a live API and just need to make usage payable fast.
Open Multi-Language Docs
MCP-Assisted
Agent Runtime
Pair the bundled MCP runtime with AgentPay-aware flows when an agent needs session checks, recovery guidance, and safer paid execution.
Best when an agent must decide whether to continue, ask for fuel, or switch into recovery guidance.
Open Agent Docs
Pick Your Use Case
See Your Path In One Glance
You should be able to tell quickly whether TDM fits your API, open library, artifact sale, or agent runtime before reading the deeper docs.
Open Library
Keep The Repo Public
Best for
You publish code on GitHub but want agents to pay for live usage.
Use it for
Hosted API calls, premium query endpoints, and paid tool execution on top of an open codebase.
Flow
Open Repo
Price Hosted Usage
Share Buy Link
Start With
tdm make payable your-api-url
API Or File
Charge For What People Use
Best for
You already have a route, hosted file, dataset, or paid artifact and want a fast go-live path.
Use it for
Per-call APIs, premium downloads, checkout links, and optional paid unlock flows.
Flow
Connect Once
Make Payable
Accept Payments
Start With
tdm connect then make payable
Agent Runtime
Run Paid Agents Safer
Best for
You operate agents that need session checks, spend guardrails, and recovery guidance.
Use it for
Session Gas Tank flows, MCP-assisted runtime decisions, sweep recovery, and repeated automation.
Flow
Agent Checks
TDM Guidance
Continue Or Recover
Start With
agentpay plus mcp runtime
TDM For Obsidian
Price A Note And Share A Paid Path
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.
Open Note
Make Payable
Share Or Unlock
Good for premium notes, paid knowledge drops, and creator-only unlock flows.
What TDM Actually Does
Flat Context For Humans, Bots, And Search
For Developers
Make APIs, routes, tools, and optional paid content payable through one SDK or a protocol-first HTTP contract.
For Agents
Let AI agents spend from standard balance or Session Gas Tank, with recovery guidance through MCP-aware runtime tooling.
For Sellers
Route paid usage into seller credits and payout flows without forcing a custom integration stack for every language.
Key Entities
TDM SDK, protocol-first HTTP, Session Gas Tank, seller payouts, MCP runtime guidance, Solana, Base, and USDC.
Primary Use Cases
Paid APIs, monetized files, agent tools, premium content, machine-to-machine transactions, and multi-language service integrations.
FAQ
What is TDM?
TDM is a machine-payments protocol for APIs, agent tools, optional content unlock, and AI runtimes. It gives teams a programmable way to turn usage into paid access and settlement flows.
Who is it for?
Developers, platforms, publishers, and agent builders who want monetized APIs, paid tool execution, optional premium content, or machine-to-machine transaction rails.
How do teams integrate?
Teams can integrate through the TDM SDK, a protocol-first HTTP contract, or MCP-assisted runtime guidance depending on the language and workflow they use.
What does TDM charge?
Pricing and fee policy should be treated as deployment-level product configuration. Public docs should focus on the authorize and payout contracts rather than hard-coded fee thresholds.
The TDM Stack
Architecture for Autonomous Commerce
01
Settlement Rail
A unified payment rail for paid access, programmable pricing, and settlement across buyers, sellers, and platform flows.
02
Session Gas Tank
Selected agents can run on prepaid balance. Fund once, then let high-frequency usage flow through one reusable spending lane.
03
MCP Runtime
A focused stdio layer for session-state checks. Use it when agents need to decide between continuing, asking for fuel, or suggesting sweep recovery.
04
Protocol-First Reach
JS teams can use framework-mode wrappers, while Python, Go, Java, Rust, C, and C++ clients can call the same public HTTP contract directly.
Powering Agentic Web3
Official Settlement, Recovery, And Payout Integration
Solana
STABLES
Base
Squads
Jupiter
MCP
Ready to make it payable?
Start integrating TDM today. Build paid APIs, files, and agents
on one programmable settlement layer.