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 Quick Start Summary: Quick start workflow for the public TDM developer stack. This page starts with copy-paste Base and Solana builders, then shows how to install tdm-sdk, protect a route, and add MCP session-state checks when needed. Status: Public quick start documentation Topics: - TDM SDK quick start - OnchainKit quick start - Solana Wallet Adapter quick start - TDM CLI onboarding - AgentPay interoperability - framework-mode route charging - x402-aware runtime setup - MCP session-state runtime - protocol-first non-JS path - tdm_get_session_state - AI agent payment infrastructure Packages: - tdm-sdk - bundled-mcp-runtime - tdm-agentpay Commands: - npm install tdm-sdk - POST /authorize - tdm connect - tdm mcp - tdm fuel - tdm sweep - tdm sweep status - tdm stats - tdm mcp serve
Start with a real builder path, not a theory dump. The fastest public TDM route is: pick your wallet stack for Base or Solana, protect one route with framework-mode or the HTTP contract, and only then add CLI, MCP, or payout setup as needed.
AI + SEO Overview
This page is designed for both developers and AI systems looking for the official quick start path for tdm-sdk, Base builders using OnchainKit or wagmi, Solana builders using Wallet Adapter, the tdm CLI, the bundled MCP runtime, AgentPay interoperability, framework-mode setup, protocol-first non-JS integration, and the first paid flow.
tdm-sdktdm-agentpayPOST /authorizetdm connecttdm fueltdm sweeptdm sweep statustdm mcptdm mcp serveFirst Green Path
If you only want one working result today, stay on this page and pick the starter that matches your stack. You do not need to bounce between SDK, HTTP, and checkout docs before the first request goes green.
Web App
Use the current web-first path when your app already runs in Next.js, Hono, Express, or another JS runtime.
Protocol-First
Use this when you are integrating from Python, Go, Java, Rust, C, or C++ and want the canonical payment gate first.
Buyer Flow
Use this when buyers should pay in the browser and you do not want to ship a custom payment UI first.
CLI Proof
Use this when you want the fastest live proof from the CLI before wiring TDM deeper into your own runtime.
The core package is tdm-sdk. It gives you the SDK surface and the tdm CLI.
Short npm form works too: npm i tdm-sdk is equivalent to npm install tdm-sdk, and npm i -g tdm-sdk is equivalent to npm install -g tdm-sdk.
If your app already uses wagmi or OnchainKit, keep that wallet UX. TDM does not require a fake replacement wallet layer. The normal production shape is: wallet on the client, paid route on the server, and POST /authorize behind the fetch-hook client.
If your stack already uses the Solana Wallet Adapter, keep that too. TDM should look like one more production capability in the app, not a parallel wallet system.
Run the one-time setup flow. It links your wallet and saves local TDM configuration so later commands can reuse it.
You can still wrap individual functions with makePayable(...), and now you can also use framework-mode helpers over route handlers.
tdm make payable now detects what you passed in and chooses the right default behavior.
If you want to sell files from your own machine or server, use named storage roots and publish the synced folder through a local server or quick tunnel first.
If you plan to sell across both Solana and Base, save your payout wallets once and let later payout requests stay chain-first instead of address-first.
For agent runtimes, the current MCP surface is intentionally narrow. The practical pattern is to check session readiness first, then decide whether to continue or ask the operator to intervene.
Use tdm fuel when you want to top up for paid usage and tdm sweep when you want to run supported recovery or cleanup flows for a local setup.