Enterprise DNA
M MCP Servers Developer low

Agentic Terminal Directory

by ai.agenticterminal

Agent commerce directory for OP-verified Lightning, BOLT12, L402, and USDT merchants

AT

MCP

Agentic Terminal Directory

Added 1 June 2026

Overview

A directory of merchants verified by the Observer Protocol that support Lightning, BOLT12, L402, and USDT payments. Built in TypeScript, it provides a structured list for developers integrating agent commerce. Merchants are OP-verified to ensure compatibility and trust.

Best for

Best for
Developers building agent commerce systems needing a verified merchant directory for Lightning and USDT payments.

Use cases

  • Discover verified merchants for agent-to-agent payments
  • Integrate Lightning, BOLT12, or L402 payment options into agent workflows
  • Validate merchant support for USDT and other payment protocols

Notes

A directory of merchants verified by the Observer Protocol that support Lightning, BOLT12, L402, and USDT payments. Built in TypeScript, it provides a structured list for developers integrating agent commerce. Merchants are OP-verified to ensure compatibility and trust.

0 stars on GitHub. Last updated 2026-05-21. Licensed MIT.

Use cases

  • Discover verified merchants for agent-to-agent payments
  • Integrate Lightning, BOLT12, or L402 payment options into agent workflows
  • Validate merchant support for USDT and other payment protocols

Pros

  • Open-source and written in TypeScript for easy integration
  • Supports multiple payment protocols (Lightning, BOLT12, L402, USDT)
  • Merchants are OP-verified, reducing fraud risk

Cons

  • Limited merchant adoption with 0 GitHub stars suggests early stage
  • Only covers OP-verified merchants, excluding many potential vendors
  • Narrow focus on specific payment protocols may not suit all agent commerce use cases

Indexed from mcp-official-registry and enriched against its public facts.

Pros

  • Open-source and written in TypeScript for easy integration
  • Supports multiple payment protocols (Lightning, BOLT12, L402, USDT)
  • Merchants are OP-verified, reducing fraud risk

Cons

  • Limited merchant adoption with 0 GitHub stars suggests early stage
  • Only covers OP-verified merchants, excluding many potential vendors
  • Narrow focus on specific payment protocols may not suit all agent commerce use cases