_ registry / mcp streamable-http · checked 1h ago

billify-pay

https://billify.org

Registry code: cecac22d4976a3d6

api record

Pay Billify invoices. get_invoice shows what an invoice link is for; verify_seller checks the seller in public registers before you pay; pay_invoice uses x402 v2 (exact USDC on Base, eip155:8453): call without payment, sign the requirement, call again with _meta["x402/payment"]. Amounts include a few millionths that identify the invoice; pay exactly what is asked.

endpoint
https://billify.org/mcp/pay
protocol
streamable-http ·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 billify-pay live?
Partly — its last checks failed now and then (checked 1h ago). It answered 0% of checks over the last 30 days.
Is billify-pay free to use?
Not measured yet.
What tools does billify-pay have?
3 tools: verify_seller, get_invoice, pay_invoice.
Is billify-pay 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
degraded
uptime, 30 days
0%

90 days 0%· all time 0%

latency
—

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → degraded· timeout after 20000ms
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • verify_seller unknown never probed

    Before paying: check the seller of an invoice in the public registers (ANAF for Romanian CUIs, VIES for EU VAT numbers): registered name, whether it matches the invoice, VAT registration and whether the company is active. Returns warnings to act on.

    mcp-tool

    {
  "type": "object",
  "required": [
    "invoice"
  ],
  "properties": {
    "invoice": {
      "type": "string",
      "description": "The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_invoice unknown never probed

    Look up a Billify invoice from its public link: seller, amount, status, and whether and how it can be paid with x402 (USDC on Base).

    mcp-tool

    {
  "type": "object",
  "required": [
    "invoice"
  ],
  "properties": {
    "invoice": {
      "type": "string",
      "description": "The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • pay_invoice unknown never probed

    Pay a Billify invoice with x402 v2 over MCP. Call it once without payment to receive the PaymentRequired (exact USDC on Base); sign it and call again with _meta["x402/payment"]. The invoice is marked paid when the facilitator settles.

    mcp-tool

    {
  "type": "object",
  "required": [
    "invoice"
  ],
  "properties": {
    "invoice": {
      "type": "string",
      "description": "The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…)"
    }
  },
  "additionalProperties": false
}
    arguments 13 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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cecac22d4976a3d6.

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

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cecac22d4976a3d6/badge.svg)](https://brick.blue/agent/cecac22d4976a3d6?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
70%

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
0

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.