Agentic Terminal Directory
VerifiedDiscover OP-verified merchants accepting Lightning, BOLT12, L402, and USDT.
What is the Agentic Terminal Directory MCP server?
The directory indexes merchants selling products, services, APIs or content who accept Lightning, BOLT12, L402 or USDT on any chain. Every record carries an Observer Protocol trust tier and an agent-callable integration tier. Data is stored as individual JSON files validated against Draft 2020-12 JSON Schema.
Six tools expose search, retrieval, rail verification, category and rail listing, plus caller identification. Reads are ungated; anonymous agents receive full Tier 1-2 data. An optional DirectoryAccessCredential only raises rate limits and unlocks reviews.
Install & connect
Add this to your MCP client config. Pick your client below and copy.
{
"mcpServers": {
"directory": {
"url": "https://mcp.agenticterminal.ai/mcp"
}
}
}Tools it exposes
6 tools your AI client can call once connected.
search_merchants— Search merchantsget_merchant— Retrieve a merchantverify_payment_endpoint— Verify payment endpointlist_categories— List categorieslist_rails— List railswhoami— Identify callerExample prompts
Once connected, try asking your AI client:
Security & permissions
Remote HTTPS endpoint at https://mcp.agenticterminal.ai/mcp requires no API keys for read access. Anonymous agents receive all public merchant data.
What you can do with Agentic Terminal Directory
Find Lightning merchants
An agent searches for merchants accepting BOLT12 offers in a given category before initiating payment.
Verify integration tier
Before checkout, the agent calls verify_payment_endpoint to confirm the merchant supports structured handoff.
List supported rails
The agent retrieves the current list of rails and USDT chains to decide which payment method to propose.
How to use Agentic Terminal Directory
- 1Add the server URL to your MCP client config under mcpServers.
- 2Connect using the streamable-http transport.
- 3Call list_categories or list_rails to explore available filters.
- 4Use search_merchants with desired criteria to find records.
- 5Retrieve full merchant objects with get_merchant when needed.
Agentic Terminal Directory: pros & cons
Pros
- +Schema-validated merchant data with clear trust tiers
- +No payment credentials or secrets required for discovery
- +Direct merchant links keep agents outside the payment path
- +Public anonymous access to all Tier 1-2 records
Cons
- –Tier 3 chain-anchored attestations not yet live
- –Write access and higher limits require separate Observer Protocol credential
- –Pre-v1 status means data and endpoints may still change
Frequently asked questions
No. Reads are ungated and anonymous agents see all public data.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…