Preparing tokens&
Loading the next builder or enterprise surface.
LoadingPreparing page
Loading product graph, proof, and adoption context.
LoadingInstall where builders already work
Builders should not browse a directory when they are shipping. The free Tokens& Agent Pack gives coding agents stack choices, perks, Build Packets, launch proof steps, and approval boundaries from the workflow they already use.
agent-pack
Public manifest: /.well-known/tokensand-agent-pack.json
OpenAPI
https://tokensand.com/openapi.json
MCP config
https://tokensand.com/api/workflow/mcp-config
Skill file
https://tokensand.com/agents/install/SKILL.md
Codex plugin
plugins/tokensand-agent-pack
Cursor plugin
plugins/tokensand-cursor-plugin
Bring Build Packets, saved stack context, enterprise session analysis, perks, and proof workflow guidance into Codex.
Install the Tokens& Codex plugin for public stack search and enterprise session briefs, then add scoped credentials when private project or workspace context is needed.
Get configLet Cursor ask for Tokens& builder or enterprise context before implementation, session follow-up, and proof publishing.
Open the installer for public stack search and enterprise session briefs. Add a scoped workflow token later for private Build Packets and project proof.
Open installerGive Claude Code the selected stack, cost, safety, docs, and proof plan without copying website text.
Use the same Tokens& MCP server command. Add DAI_TOKEN only when private project context is required.
Get configGive every agent host one stable package specifier and avoid cache misses from versioned tarball URLs.
Publish the CLI package publicly, then use the npm package name instead of the hosted tarball in every MCP config.
Get configKeep stack decisions and project proof visible beside the repo.
Use the Codex IDE extension or a compatible MCP client. Public search works first; scoped tokens unlock project context.
Get configVerify native tools loaded
Use Tokens& get_account_mode. If native tools are loaded, call search_tools for "support agent with auth and RAG" and return the receipt ID. If not, tell me to rerun codex mcp list and restart Codex.Copy the setup for your agent. Raw configuration stays available as a fallback when an installer cannot be used.
Codex command
codex mcp add tokensand --env DAI_AGENT_INSTALL_SESSION=__TOKENSAND_AGENT_INSTALL_SESSION__ -- npx -y @dev-adoption/cli@latest mcp serve --api https://tokensand.comCodex TOML fallback
[mcp_servers.tokensand]
command = "npx"
args = ["-y", "@dev-adoption/cli@0.1.10", "mcp", "serve", "--api", "https://tokensand.com"]
env = { DAI_AGENT_INSTALL_SESSION = "__TOKENSAND_AGENT_INSTALL_SESSION__" }Cursor / MCP JSON
{
"mcpServers": {
"tokensand": {
"command": "npx",
"args": [
"-y",
"@dev-adoption/cli@0.1.10",
"mcp",
"serve",
"--api",
"https://tokensand.com"
],
"env": {
"DAI_AGENT_INSTALL_SESSION": "__TOKENSAND_AGENT_INSTALL_SESSION__"
}
}
}
}Claude Code
claude mcp add --env DAI_AGENT_INSTALL_SESSION=__TOKENSAND_AGENT_INSTALL_SESSION__ --transport stdio tokensand -- npx -y @dev-adoption/cli@0.1.10 mcp serve --api https://tokensand.comnpm after publish
DAI_AGENT_INSTALL_SESSION=__TOKENSAND_AGENT_INSTALL_SESSION__ npx -y @dev-adoption/cli@0.1.10 mcp serve --api https://tokensand.comBuilder activation bridge
The highest-leverage next step after install intent is a tagged build packet or proof draft. These starters keep agent-native visitors on an owned path that can produce saves, signups, and shares.
Builders searching for a repeatable Codex bug-triage workflow need issue intake, reproducible checks, severity routing, regression tests, and pull-request proof. Authenticate first, preserve that exact query in stack search, then save the resulting Build Packet instead of ending at a generic install.
MCP server release sprint
Turn the install into a stack decision for an agent-native product instead of a copied config with no next action.
Support agent with auth and memory
Move a coding-agent install into a saved build recommendation while the builder is still deciding the backend, auth, and retrieval stack.
RAG over internal docs
Give install-intent builders a prefilled path into retrieval, vector, and deploy decisions before they leave for generic docs search.
Agent credit runway
Credit intent converts better when the builder leaves with a build packet, usage plan, and proof draft tied to the official program they are checking.
Use this path when the bottleneck is GitHub Actions, Codespaces, Copilot, and the agent loop around pull requests.
Startup credits for GitHubUse this path when the next decision is model routing, rate limits, evaluation, and a cost-controlled agent prototype.
OpenAI for StartupsUse this path when the workflow depends on Claude API access, Claude Code setup, priority limits, and a reproducible agent demo.
Anthropic startup termsChoose the stack
Ask Tokens& search_tools or build_brief before code changes when the user is choosing tools, backend, auth, data, deployment, cost, credits, APIs, or proof path. Require live directory rows, DB facets, tracked actions, and a receipt ID for agent-context answers.
Find useful builder offers
Check public perks and credits that match the selected stack. Do not imply a perk is guaranteed until the user claims it.
Ship an Agent Skill
When the repo contains a public SKILL.md or the user gives a SKILL.md URL, call publish_agent_skill without confirm first. Review the parsed draft with the user, then call it again with confirm: true to create the private dashboard draft in Tokens&. Public publishing is a separate authenticated dashboard action after the install path is verified.
Publish proof only after review
Draft repo, demo, stack, launch source, and notes first. Public proof publishing requires explicit human approval.
Record usage receipts
When a builder adds server-side instrumentation, use @tokensand/adoption trackUsageReceipt for model, MCP, API, spend, latency, and workflow proof. Keep tracking keys server-side and never include raw prompts, secrets, private payloads, or source code in receipt metadata.
Return enterprise session signal
Use get_account_mode first, then call enterprise_session_brief for source-labeled funnel rates, costs, ICP segment guidance, session format, dashboard handoff, and proof boundaries. Self-reported proof is not verified until first-party, public-source, consented, or aggregate-safe evidence clears the gate.
Draft adoption motion
Draft the adoption session, ICP invite batch, Invite partner company motion, or proof plan inside the agent. For sessions, accept sourceProvider luma/partiful/eventbrite/zoom/manual plus a public sourceUrl, never API keys. Require dashboard approval before any Tokens& write or external send.
Private saved stacks, project context, live enterprise tenant metrics, and write actions require a signed-in session or scoped workflow token.
Tokens& creates tracking, partner intake, ICP preview, and proof. It does not create Luma/Zoom/Eventbrite pages or send external invites without approval.
Public adoption reads are aggregate and source-labeled; raw developer identity and tenant-scoped enterprise metrics stay private.
Enterprise teams add offers. Builders claim them inside the agent workflow. Projects publish proof. Vendors get source-labeled adoption signals and improve the next offer.
Add builder offer