Is at-directory live?

Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.

Is at-directory free to use?

Yes — the hub reached it with no key and no payment.

What tools does at-directory have?

6 tools: get_merchant, whoami, verify_payment_endpoint, search_merchants, list_rails, list_categories.

Is at-directory safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 2h ago

at-directory

https://mcp.agenticterminal.ai

Registry code: 9de6e60c5de88adf

api record

Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

from a public catalogue that lists it, not from the operator

endpoint: https://mcp.agenticterminal.ai/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is at-directory live?: Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is at-directory free to use?: Yes — the hub reached it with no key and no payment.
What tools does at-directory have?: 6 tools: get_merchant, whoami, verify_payment_endpoint, search_merchants, list_rails, list_categories.
Is at-directory safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

98.1%

90 days 98.9%· all time 99.1%

latency

654ms

last good check

priced tools

of 6 tools

_ answered our checks, 90 days 570 checks · signed record

2026-10-26 03:35 degraded → live
2026-10-26 00:35 live → degraded· HTTP 520
2026-10-20 20:56 degraded → live
2026-10-20 18:55 live → degraded· timeout after 20000ms
2026-10-20 16:22 degraded → live

_ what it is for

topic: payments & commerce payment infrastructure
used for: find merchants accepting agent payments
verify a merchant payment endpoint
list supported payment rails
takes → gives: text → data
tools: 6 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 6 tools

3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

search_merchants reads open 5h ago

Search OP-verified merchants by rail, chain, category, agent-callable tier, trust tier, and free text. Ranked by trust tier then verification recency.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "rail": {
      "enum": [
        "lightning",
        "bolt12",
        "l402",
        "usdt"
      ],
      "type": "string"
    },
    "chain": {
      "enum": [
        "tron",
        "ethereum",
        "solana",
        "bsc",
        "polygon",
        "arbitrum",
        "base"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "exclusiveMinimum": 0
    },
    "query": {
      "type": "string"
    },
    "category": {
      "type": "string"
    },
    "accepts_usdc": {
      "type": "boolean"
    },
    "trust_tier_min": {
      "enum": [
        1,
        2,
        3
      ],
      "type": "number"
    },
    "agent_callable_tier": {
      "enum": [
        "full-api",
        "structured-handoff",
        "human-checkout"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}

arguments 57 lines

list_rails reads open 5h ago
List supported payment rails and their current merchant counts.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
list_categories reads open 5h ago
List the category taxonomy with merchant counts.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

get_merchant reads unknown 25h ago

Get the full record for one merchant including all rails, payment endpoints, and OP attestation. Tier 2+ requires an AT credential.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}

arguments 14 lines

whoami reads unknown never probed
Report the resolved credential state and rate limits for the calling agent.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

verify_payment_endpoint reads unknown never probed

Run a live check against a merchant's declared payment endpoint for a rail. Returns health, detail, and rail-specific evidence.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "merchant_id",
    "rail"
  ],
  "properties": {
    "rail": {
      "enum": [
        "lightning",
        "bolt12",
        "l402",
        "usdt"
      ],
      "type": "string"
    },
    "merchant_id": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}

arguments 24 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9de6e60c5de88adf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9de6e60c5de88adf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/9de6e60c5de88adf/badge.svg)](https://brick.blue/agent/9de6e60c5de88adf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.