Who it's for

For teams that still need fax and would rather not run it.

FaxDev serves five kinds of teams on one platform. Each section starts with the moment it changes.

Resellers and managed service providers

At month end you open the org console and see retail, wholesale, and margin for every sub-account. No spreadsheet.

Sell fax under your own brand without running a single fax server.

  • Account per customer. Create sub-accounts in the console or through the API.
  • Your price, your margin. Set each customer's retail price and monthly page cap. Bill them yourself, or let us bill them for you.
  • Your brand. Logo, colors, support email, and your own app hostname. One organization webhook covers every customer.
  • Automate provisioning. Organization-level API keys and MCP access let your own tooling set customers up.
  • MSPs
  • telecom resellers
  • practice software vendors

Clinics and healthcare offices

A referral arrives while the front desk is on the phone. By the time they hang up it is in three inboxes and on its way to your EHR integration's webhook.

Get referrals, records requests, and prescriptions to the right people, and know who opened them.

  • Route by number. Inbound faxes go to the inbox and to the email addresses you choose for each number.
  • Every read on record. Every document view and download is audit-logged, and you choose how long documents are kept.
  • HIPAA-ready when you need it. The HIPAA add-on includes a BAA, enforced two-step sign-in, and link-only notifications. It supports HIPAA compliance; it is not a certification. See HIPAA fax.
  • referrals
  • records requests
  • prescriptions

Law, accounting, and insurance firms

A motion goes out at 4:58. The first try hits a busy line, the retry goes through, and the record shows both attempts, page by page.

Send filings and signed documents, and keep a record of every attempt.

  • Full attempt history. When it dialed, which route, how many pages went through, and why a try failed.
  • Cover pages. Optional per fax, from your account's template.
  • Billed once. Retries and carrier failover happen on their own; you pay once, and only on success.
  • filings
  • signed agreements
  • claims

Logistics, freight, and field operations

A signed bill of lading comes back from a shipper's fax machine and lands in your TMS as a webhook, matched to the load before dispatch looks up.

Move bills of lading, rate confirmations, and proof of delivery straight from the dispatch system.

  • One HTTP call. Send from your TMS or dispatch system with a client reference you can match later.
  • File automatically. Received faxes arrive as signed webhooks your system can file without a person.
  • Many numbers. Contacts and several fax numbers per account, with a default sending number.
  • bills of lading
  • rate confirmations
  • proof of delivery

Developers and AI agent builders

You build against a sandbox key that never dials or bills, then hand your agent a scoped key and watch it call send_fax on its own.

Add fax to a product or an agent with an API that behaves like the rest of your stack.

  • Upload, then send. PDF, TIFF, JPEG, or PNG. Sandbox keys (bfx_test_) complete faxes without dialing or billing.
  • Signed webhooks. HMAC-SHA256 signed, carrying the same fax object the REST API returns.
  • MCP that matches the key. The MCP server is generated from the REST API, so an agent sees exactly the operations its key allows.
  • SaaS products
  • internal tools
  • AI agents

See where FaxDev fits.

Tell us what you fax today and how much of it. Developers can start in the sandbox right away.