# FireBuddy

> Pay-by-bank payments and invoicing for Irish and UK businesses, on the
> merchant's own Fire (fire.com) account. FireBuddy is software — money
> settles directly to the merchant's regulated bank account and never touches
> FireBuddy. Fees: flat €0.30/£0.30 per payment, any size, drawn from prepaid credit. EUR and GBP.

FireBuddy is built to be driven by AI agents as well as humans. The REST API
is idempotent (invoices by `invoice_number`, payment requests by request), a
payment is only ever "paid" when the bank confirms that exact payment
(`status: completed` — enforced by a database constraint, not convention), and
in-flight is explicit (`in_flight` / `settled` fields; the `payment.authorised`
webhook always carries `settled: false`). An agent can create and send
invoices, take payments, check settlement, chase unpaid invoices and produce a
VAT summary — but cannot mark money as received, and neither can anyone else:
only the bank's confirmation can.

## Connect an agent

- [MCP server (Streamable HTTP)](https://mcp.firebuddy.info):
  add as a custom connector in Claude, or any MCP client. 17 tools:
  quick_invoice, create_invoice, send_invoice, list_invoices, check_payment,
  create_payment_link, chase_unpaid, receivables_review, vat_summary,
  account_balances, list_transactions, create_offer, and more. OAuth
  (login-and-approve) or a `fb_live_…` API key from the merchant's dashboard.
- [Agents guide](https://firebuddy.info/agents): what an agent can and
  cannot do, the settlement truth model, and example prompts.

## Docs

- [API documentation](https://firebuddy.info/docs.html): quickstart, REST API,
  webhooks, embed widget.
- [OpenAPI specification](https://firebuddy.info/docs/api/openapi.yaml): the
  source of truth for every route and schema.
- Base URL: `https://srjrxyobhfegimgqfpor.supabase.co/functions/v1/firebuddy-api`
  — auth `Authorization: Bearer fb_live_…` (per-merchant key).

## Key facts for agents

- Amounts are major units (49.99 = €49.99).
- A payment is paid only at `status: "completed"` / `settled: true`. Never
  fulfil on `in_flight` or on the `payment.authorised` webhook — an authorised
  payment can still fail.
- `POST /invoices` is idempotent by `invoice_number`; retries are safe.
- Webhooks: flat JSON, `x-firebuddy-event` + `x-firebuddy-signature`
  (HMAC-SHA256 of the raw body). Events: payment.authorised,
  payment.completed, payment.failed, invoice.paid.
- Not a card processor: no cards, no card-on-file, no chargebacks. Payers
  authenticate at their own bank per payment (native SCA).

## Policies

- [Privacy policy](https://firebuddy.info/privacy.html)
- [Terms](https://firebuddy.info/eula.html)