ai.agenticterminalPublished by agenticterminal.aiOfficial publisherv1.0.0Updated Oct 24, 2026
Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.
Lets an assistant search and inspect merchants that accept agentic payments over Lightning, BOLT12, L402 or USDT, and check their payment endpoints.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.agenticterminal%2Fdirectory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"agentic-terminal-directory": {
"type": "http",
"url": "https://mcp.agenticterminal.ai/mcp"
}
}
}Where agents discover OP-verified merchants on the rails Bitcoin and Tether actually use.
AT Directory indexes merchants that sell products, services, APIs, or content and accept Lightning, BOLT12, L402, or USDT (any chain), with trust attestations issued through Observer Protocol. It is the verified, agent-callable layer on top of the fragmented agent-payment landscape. It is not in the payment path — agents discover here and pay merchants directly.
@agenticterminal/mcp-server, hosted at mcp.agenticterminal.ai.Pre-v1, active build. Target: week of 2026-05-18 for a live Tether-meeting demo. v1 ships Tiers 1–2.
Six tools: search_merchants, get_merchant, verify_payment_endpoint, list_categories, list_rails, whoami. Reads are ungated — anonymous agents see all tiers and can transact with no setup. An Observer Protocol DirectoryAccessCredential raises rate limits and unlocks write access (reviews), but is not required to discover or transact. Full reference: agenticterminal.ai/api-docs.
Local MCP with the mock verifier (until the real AT route lands):
Every merchant carries two orthogonal signals — read both:
full-api · structured-handoff · human-checkout.The trust tier gates nothing. Reads are ungated, every tier is visible to anonymous agents, and an agent can transact with a Tier 1 merchant with no setup. The tier is evidence for a caller to weigh, not a decision this directory has made on its behalf. Nothing is refused on the basis of it.
Schema is enforced in CI (pnpm validate-data) and on every load. USDT rails require a chain; Tier 2+ non-integrated records require an op_attestation_url; an op_trust_tier of 3 is rejected on ingest, which is why the model above stops at 2.
See CONTRIBUTING.md. Merchants and researchers submit by email to
[email protected]; accepted entries land at Tier 1 until verified.
The self-registration form at /submit is not operational. apps/web/app/submit/page.tsx has
had TALLY_FORM_ID = 'TODO' since 883c183 (2026-06-22, which replaced the earlier GitHub-issue form)
and no commit since has changed it, so the page renders an email fallback and embeds no form.
apps/web/netlify/functions/submit-merchant.ts exists and is complete, but it needs
TURNSTILE_SECRET_KEY, GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY and GITHUB_INSTALLATION_ID in the
Netlify environment and nothing in this repo shows whether they are set. This README and
CONTRIBUTING.md advertised the form as the working route anyway until 2026-09-15, when an inbound
bounty submission pointed it out. Do not re-advertise it until the form ID is set and a test
submission has actually opened a PR.
MIT.
Source: README.md at commit 12e7de4
Search OP-verified merchants by rail, chain, category, agent-callable tier, trust tier, and free text. Ranked by trust tier then verification recency.
railchainlimitquerycategoryaccepts_usdctrust_tier_minagent_callable_tierGet the full record for one merchant including all rails, payment endpoints, and OP attestation. Tier 2+ requires an AT credential.
idrequiredRun a live check against a merchant's declared payment endpoint for a rail. Returns health, detail, and rail-specific evidence.
railrequiredmerchant_idrequiredList the category taxonomy with merchant counts.
Takes no parameters.
List supported payment rails and their current merchant counts.
Takes no parameters.
Report the resolved credential state and rate limits for the calling agent.
Takes no parameters.
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
// Hosted (recommended, no install){ "mcpServers": { "at-directory": { "url": "https://mcp.agenticterminal.ai/mcp" } } }npm install -g @agenticterminal/mcp-server # local alternativedata/merchants/ One JSON file per merchant (the source of truth).data/schema/ JSON Schema (Draft 2020-12) for merchant records.data/categories.json Category taxonomy.data/rails.json Supported rails + USDT chains.data/LOGO-AUDIT.md Logo sourcing checklist.packages/core/ Types, schema-validated load, search/filter.packages/mcp-server/ stdio + hosted HTTP MCP server, rail verification.packages/skill/ SKILL.md (canonical).apps/web/ Next.js static directory + Netlify Functions.deploy/mcp-server/ Dockerfile, systemd unit, DEPLOY runbook.scripts/ Data validation (and one-time crawl tooling).pnpm installpnpm -r test # core + mcp-server unit/integration testspnpm -r typecheckpnpm validate-data # schema-validate every merchant recordpnpm -F @at-directory/web dev # web at localhost:3000pnpm -F @agenticterminal/mcp-server start:stdio # MCP over stdiopnpm -F @agenticterminal/mcp-server exec tsx src/dev/mock-verifier.ts &AT_VERIFIER_URL=http://127.0.0.1:8787 \ pnpm -F @agenticterminal/mcp-server start:stdio