HTTP API · MCP server · Web panel
Fax infrastructure for people, systems, and agents.
A referral arrives while the front desk is on a call. By the time they hang up it is in three inboxes and on its way to your systems. FaxDev sends and receives fax through an API, an MCP server, and a web panel, and bills only for pages that arrive.
Three ways in
One fax underneath, however you send it.
A person in the web panel, a script on the API, and an agent over MCP all create the same fax, with the same retries, the same audit trail, and the same bill.
HTTP API
From a PDF to a delivered fax in three calls.
Your billing run finishes invoice 1042 at midnight. It uploads the PDF, sends it with an Idempotency-Key, and when the network blips it simply repeats the request. No second fax. The answer comes back as a signed webhook, or whenever you poll.
- Idempotent creates for safe retries
- Problem+JSON errors with stable codes
- Sandbox keys run the pipeline without dialing
MCP server
Your agent files the motion at 4:58.
A paralegal asks the filing assistant to fax a signed motion before the clerk's office closes. The agent calls send_fax, then get_fax, and comes back with the pages delivered and the minute it completed. Its key can do only what you scoped it to do.
- Tools generated from the REST API
- Filtered by scope, so agents never see what they cannot call
- Short-lived document URLs, not file bytes in transcripts
connecthttps://api.faxdev.com/mcpwith your API key
Web panel
Everyone else just opens the inbox.
Front desk, records, billing: they see received faxes with unread counts, send with a cover page, and watch a fax go from queued to succeeded, page by page, with every attempt on the record.
- Inbox and sent with live status
- Numbers, contacts, users, and API keys
- Your brand on your own hostname, for resellers
Delivery assurance
We get it there.
Every fax goes out over multiple independent carrier networks. A busy line, no answer, or failed handshake is retried and rerouted automatically, and when the primary routes cannot complete it, an alternate route takes over (it may show a different caller ID). You get a record of every attempt and pay only for pages that arrive.
Outbound: your app through the REST API, an AI agent through MCP, a person in the web panel, or an approved sender by email submits a document. FaxDev renders it into fax pages, verifies the number and your limits, and routes it over one of several independent carrier networks. A busy line, no answer, or a failed handshake is retried and rerouted to another network automatically, and if the primary routes cannot complete it, an alternate route is used, which may show a different caller ID. Whichever network completes it, the fax arrives at the recipient's fax machine. Inbound: a sender's fax reaches the number you own, FaxDev stores it encrypted and audits every read, and delivers it to the inbox, to email recipients, and to a signed webhook.
- Outbound
- Inbound
- Retry and alternate route
Who it's for
Built for the people who still run on fax.
Five kinds of teams, one platform. What changes is the moment it saves.
At month end you open the org console and see retail, wholesale, and margin for every sub-account. No spreadsheet.
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.
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.
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.
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.
Platform
Everything a fax needs, nothing it does not.
API first
Everything the web panel does is a documented REST call. Creates take an Idempotency-Key, so a retry never sends a fax twice.
MCP for agents
The same API is an MCP server. An agent with a scoped key can send, check status, and fetch received documents.
White-label for resellers
A sub-account per customer, your own retail price and page caps, and a branded app on your own hostname.
Webhooks and email
Each received fax lands in the inbox, goes to the number's email recipients, and hits your HMAC-signed webhook. Email comes from [email protected]: allow-list it once.
Delivery, not just dialing
Busy lines, no-answers, and failed handshakes are retried and rerouted across independent carrier networks on their own. Every attempt is on the record.
Audit and retention
Every document view and download is logged. Each account picks how long documents are kept, from 30 days to seven years.
Security
Faxes carry sensitive documents. We treat every one that way.
Controls, not certificates. Handling protected health information? The HIPAA add-on includes a BAA and enforces the safeguards that support HIPAA compliance. We do not claim a HIPAA or SOC 2 certification.
Encrypted at rest
Documents, database volumes, and backups. HTTPS only in transit.
Audited reads
Every view or download, by a person, a key, an agent, or our staff, is logged.
Retention per account
90 days by default, from 30 days up to seven years by choice. Then the content is deleted.
Scoped keys
Keys carry only the scopes you grant, are revocable, and are stored hashed.
Pricing
Pay for pages that arrive.
Per page, plus a monthly charge per number. A fax that fails, is cancelled, or expires costs nothing.
- Delivered outbound pagesbilled
- Received inbound pagesbilled
- Fax number rentalmonthly
- Failed, cancelled, expired faxesfree
Send your first fax today.
Start a free trial with $3 of trial credit and a card on file, or create a test key in the app, point it at the API, and watch a fax move through every state without dialing a number. FaxDev is an internet fax service, not a telephone service.