Agentic Terminal Directory
Let your agent discover OP-verified merchants that accept Lightning, BOLT12, L402, or USDT and hand off to direct payment without joining the money path.
Overview
AT Directory is a MCP server for the Build phase that lets AI agents search Observer Protocol–verified merchants and payment rails (Lightning, L402, BOLT12, USDT) without routing funds itself.
What is this MCP server?
- Six MCP tools: search_merchants, get_merchant, verify_payment_endpoint, list_categories, list_rails, whoami.
- Hosted primary endpoint at https://mcp.agenticterminal.ai/mcp; optional npm global @agenticterminal/mcp-server.
- Read tools ungated—anonymous agents can discover and transact; Observer Protocol credential raises limits and enables re
- Indexes Lightning, BOLT12, L402, and USDT rails—not in the payment path, discovery only.
- Companion web directory at agenticterminal.ai and SKILL.md for agent payment handoff patterns.
- 6 MCP tools: search_merchants, get_merchant, verify_payment_endpoint, list_categories, list_rails, whoami
- 4 payment rails indexed: Lightning, BOLT12, L402, USDT
- Hosted URL: https://mcp.agenticterminal.ai/mcp
What problem does it solve?
Builders waste days finding which merchants truly accept agent payments on fragmented Bitcoin and stablecoin rails.
Who is it for?
Agents that monetize via Lightning or USDT, indie builders demoing agentic commerce, and prototypes needing verified merchant lists without building a directory.
Skip if: Teams that only need product catalogs, generic web search, or in-path payment processing—this server discovers and verifies, it does not settle trades.
What do I get? / Deliverables
Your agent can search, verify endpoints, and complete payment handoff to merchants using six directory tools over hosted MCP.
- Hosted or local MCP connection to AT Directory
- Merchant search and payment-endpoint verification in agent workflows
- Category and rail listings for agentic checkout handoff
Recommended MCP Servers
Journey fit
Payment-capable agent flows are wired in Build; the same directory supports Validate prototypes and Grow monetization experiments. Merchant search and endpoint verification are integration tasks—you plug the MCP into the agent stack alongside wallets and APIs.
How it compares
Verified merchant-discovery MCP, not a product-catalog MCP or identity oracle.
Common Questions / FAQ
Who is AT Directory for?
Developers shipping autonomous agents that must discover and pay OP-verified merchants on Lightning, L402, BOLT12, or USDT.
When should I use AT Directory?
When prototyping or shipping agent workflows that need merchant search, rail filtering, and payment-endpoint verification before you integrate a wallet.
How do I add AT Directory to my agent?
Add mcpServers.at-directory with url https://mcp.agenticterminal.ai/mcp in your client JSON, or npm install -g @agenticterminal/mcp-server for local MCP; then call the six directory tools from your agent.