Billify payments is an MCP server published by io.github.Ovindolo, hosted at billify.org. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including get_invoice, verify_seller, pay_invoice, confirm_delivery.
Let agents verify the seller and pay Billify invoices with x402 (USDC on Base).
706 connections through 4 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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).
| Parameter | Type | Description |
|---|---|---|
| invoice * | string | The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…) |
{
"name": "get_invoice",
"title": "Get invoice",
"description": "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).",
"inputSchema": {
"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
},
"annotations": {
"readOnlyHint": true
}
}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, whether the company is active and (ANAF) whether it is in the RO e-Factura register. Also checks the IBAN on the invoice page and shows the wallet an x402 payment goes to. Returns warnings to act on.
| Parameter | Type | Description |
|---|---|---|
| invoice * | string | The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…) |
{
"name": "verify_seller",
"title": "Verify seller",
"description": "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, whether the company is active and (ANAF) whether it is in the RO e-Factura register. Also checks the IBAN on the invoice page and shows the wallet an x402 payment goes to. Returns warnings to act on.",
"inputSchema": {
"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
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| invoice * | string | The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…) |
{
"name": "pay_invoice",
"title": "Pay invoice (x402)",
"description": "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.",
"inputSchema": {
"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
},
"annotations": {
"readOnlyHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}After paying: record whether the work was delivered, as accepted or disputed (a dispute needs a note). The decision is tied to the seller's latest delivery record (see delivered in get_invoice), by its record_hash. Add reference for your own note of what you received (a URL or a content hash). With signature, an EIP-191 signature by the wallet that paid over the text this tool returns as sign_message when called without decision, the decision is recorded as proven by the payer; without it, only as made by someone holding the invoice link. An acceptance is final. It appears in the signed Invoice Passport history.
| Parameter | Type | Description |
|---|---|---|
| name | string | The agent's or person's name |
| note | string | |
| invoice * | string | The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…) |
| decision | string | one of ["accepted","disputed"] |
| reference | string | |
| signature | string | 0x-prefixed EIP-191 signature by the paying wallet |
{
"name": "confirm_delivery",
"title": "Confirm delivery",
"description": "After paying: record whether the work was delivered, as accepted or disputed (a dispute needs a note). The decision is tied to the seller's latest delivery record (see delivered in get_invoice), by its record_hash. Add reference for your own note of what you received (a URL or a content hash). With signature, an EIP-191 signature by the wallet that paid over the text this tool returns as sign_message when called without decision, the decision is recorded as proven by the payer; without it, only as made by someone holding the invoice link. An acceptance is final. It appears in the signed Invoice Passport history.",
"inputSchema": {
"type": "object",
"required": [
"invoice"
],
"properties": {
"name": {
"type": "string",
"description": "The agent's or person's name"
},
"note": {
"type": "string"
},
"invoice": {
"type": "string",
"description": "The invoice's public token (UUID) or its Billify link (billify.org/pay/…, /invoice/…)"
},
"decision": {
"enum": [
"accepted",
"disputed"
],
"type": "string"
},
"reference": {
"type": "string"
},
"signature": {
"type": "string",
"description": "0x-prefixed EIP-191 signature by the paying wallet"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Pay Billify invoices. get_invoice shows what an invoice link is for; verify_seller checks the seller in public registers before you pay; confirm_delivery records afterwards whether the work was delivered; 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.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.