!
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.
# TDM Start Here Summary: Simple onboarding guide for people who want the shortest path from install to accepting or using stablecoin payments. The main path is install, connect once, then make something payable or top up for paid usage. Status: Public onboarding guide Topics: - tdm connect - tdm make payable - stablecoin onboarding - simple payment setup - creator-friendly TDM flow Packages: - tdm-sdk Commands: - npm install tdm-sdk - tdm connect - tdm where - tdm status - tdm workspace status - tdm workspace create seller-lab --storage media --use - tdm make payable ./file.pdf --price 0.05 - tdm fuel --amount 10 --yes
This page is for people who do not want to learn the whole TDM stack first. The short version is simple: install the SDK, run tdm doctor on a fresh machine, run tdm connect once, then use the command that matches what you want to do. If you forget and jump straight into a live seller flow, the CLI can bootstrap that setup automatically.
This is the shortest honest seller path in the current MVP: install the SDK, verify the machine, connect once, and price one real asset or route. If this works, the rest of the stack can be added later.
First Result
You do not need the whole platform in your head first. Pick the first real outcome, make that green, then come back for the more advanced runtime, catalog, or payout flows.
Fastest Seller Path
Use this when you want the quickest proof that TDM is connected and can put a price in front of one real thing.
Keep Paid Usage Running
Use this when you mostly want to buy paid calls, run agents, or avoid repeating setup before every paid action.
Seller Payout Setup
Use this when you are selling and want later payout requests to stay chain-first instead of re-entering addresses every time.
TDM already ships with a conservative starter profile. It is designed to keep normal usage simple while adding friction only when something becomes risky or unusually large.
Default spending guardrails start at $10 per paid action, $25 per hour, and $100 per day.
Publisher payouts start with $100 per payout and $500 per day so large withdrawals do not behave like silent background actions.
Sensitive changes can require an extra confirmation step, and new payout destinations can be treated more carefully than routine repeat payouts.
Larger payout requests start with a 24 hour hold from $100 upward by default. That gives the account owner time to notice and respond before value leaves the system.
Scenario
Best for an API, tool call, paid route, premium note, or downloadable resource.
Scenario
Best when you want to use paid tools or run an agent without repeating setup every time.
Scenario
Best when you want to collect dust into stables or send stablecoins back out.
One-time setup. It links your wallet, creates local vault state, prepares your local payment setup, can seed the first payout wallet when that chain slot is empty, and can configure MCP support for the current project.
Local setup command for MCP-aware projects. Use it when you want to add or refresh .mcp.json without rerunning the full wallet connection flow.
Show the current live and local context in one place: vault, storage, live-mode readiness, publishes, agents, and milestone blocks.
Check whether this machine is ready for the interactive launcher, OS keyring-backed secret storage, and local TDM runtime files.
Show where the current live TDM URL, API key, session, wallet, and provider values came from across vault, OS keyring, process env, and local env files.
Focus the same report on one saved workspace when you manage a catalog, agent set, or seller contour as a reusable unit.
Attach a price to a route, tool call, file, URL, or code path after tdm connect prepares the live payment surface.
Save or replace the default external payout wallets for Solana and Base. This keeps seller withdrawals simple later because payout requests can stay chain-first.
Top up your payment workflow so paid calls can keep running.
Sweep collects leftovers into stables. Cashout sends stablecoins back to your wallet.
Review built-in protection, add app-based verification, and adjust advanced limits if your workflow needs a different risk profile.
Use the SDK function inside application code when you want to wrap a handler, route, or tool call directly in your app. This is the developer path for framework-mode integrations.
Use the CLI when you want to register a public route, URL, file, or paid unlock flow quickly without writing new wrapper code first. This is often the fastest path for hosted APIs, paid artifacts, and creator-facing delivery flows.
If you run a photo stock, content marketplace, tool platform, or API service, you can integrate the current public TDM surface today. The public path is to register payable resources and use POST /authorize on the protected call path.
If you maintain an open GitHub library, the normal TDM production path is not to sell the repository clone itself. Keep the source public, expose a live API or tool endpoint that uses the library, and make that hosted usage payable.
Human developers can still inspect, clone, and evaluate the library normally on GitHub.
Agents and external clients pay when they call the hosted route or tool surface, not when they browse the source tree.
Publish the checkout link, buy URL, or README snippet so buyers and agent operators know where paid usage starts.