Fax API for AI agents: how to send a fax with an API
To send a fax with an API, a script or an AI agent sends a fax number and a PDF, pays, and checks the status. The FaxFair agent API works over HTTP or as an MCP server, for US and Canadian numbers. A fax costs $2.49 for up to 40 pages and $6.99 for 41 to 100 pages. Payment goes in the request with USDC on Base, or comes from a prepaid API key.
How to send a fax with an API
- Get the price. Ask for a quote with the fax number in E.164 form (+1 and 10 digits) and the page count. In a URL, write the + as %2B. A quote sends nothing and costs nothing, and a bad number comes back as an error instead of a price.
curl "https://api.faxfair.com/v1/agent/quote?to=<fax number>&pages=3" - Send the PDF. Post the number and an https link to the PDF, or upload the file. An
Idempotency-Keyheader makes a retry return the same fax instead of sending a second one.curl -X POST https://api.faxfair.com/v1/agent/faxes \ -H "Authorization: Bearer <api key>" \ -H "Idempotency-Key: <unique id>" \ -H "Content-Type: application/json" \ -d '{"to": "<fax number>", "pdf_url": "https://example.com/form.pdf"}' - Pay. With a prepaid key, the price is held from the key's balance when the fax is accepted. Leave out the
Authorizationheader to pay with USDC instead: the API answers HTTP 402 with the price in aPAYMENT-REQUIREDheader. The client signs that amount in USDC on Base and sends the same request again with aPAYMENT-SIGNATUREheader. - Check the status. Read the fax by its id until the status is
deliveredorfailed. The price is taken on delivery, so a failed fax costs nothing.curl https://api.faxfair.com/v1/agent/faxes/<fax id>
| Route | What it does |
|---|---|
GET /v1/agent/quote | Prices one fax from the number and page count, without sending it |
POST /v1/agent/faxes | Sends a PDF from an https link or a file upload, and asks for payment if none is attached |
GET /v1/agent/faxes/{id} | Returns queued, sending, delivered or failed for one fax |
What a delivered status proves is in Is a fax confirmation proof your fax was received? Common reasons a fax fails are in Why is my fax not going through?
Sending a fax from an AI agent over MCP
- Connect. Point an MCP client at
https://api.faxfair.com/mcp, which speaks streamable HTTP. The client sendsinitializeand keeps theMcp-Session-Idheader it gets back, as the MCP specification requires. - Price it. Call
quote_faxwith the fax number and the page count. - Send it. Call
send_faxwith the number and an https link to the PDF. Payment works the same way as over HTTP: a prepaid key, or a 402 answered with a signed USDC payment. - Track it. Call
get_fax_statuswith the fax id until it says delivered or failed. If the fax fails, a key gets its hold back, and a USDC payment becomes credit for that wallet's next fax.
What a fax costs through the FaxFair API
| Pages | Standard | Priority |
|---|---|---|
| 1 to 40 | $2.49 | $4.98 |
| 41 to 100 | $6.99 | $13.98 |
The price is per fax, not per page, so a 30-page contract costs the same $2.49 as a one-page form. There is no monthly fee. When faxes are waiting for a line, a priority fax goes ahead of standard agent faxes and isn't held back by the cap on standard agent faxes in flight. Faxes sent from faxfair.com and the FaxFair app still go ahead of both, and with free lines priority changes nothing.
What an agent needs from a fax API
A person sending a fax can read a price page, type a card number and watch for a confirmation. An agent works only from what the API returns, so each of those steps has to exist as a field, a header or a tool.
| Need | Why it matters to an agent | FaxFair agent API |
|---|---|---|
| A price before sending | It can check a budget or ask a person before it spends | quote_fax returns the standard and priority price and sends nothing |
| A way to pay per request | No sign-up or checkout page stands between the agent and the fax | An HTTP 402 with the price, then a signed USDC payment on the retry, or a prepaid key |
| Safe retries | A timeout shouldn't send the same fax twice | An Idempotency-Key header makes a retry return the same fax |
| A status it can poll | It can tell the person whether the fax went through | get_fax_status returns queued, sending, delivered or failed |
| No charge for a failed fax | A busy line or a wrong number shouldn't cost money | The price is held when the fax is accepted and taken on delivery, so a failed fax costs nothing |
| Limits it can read | It can slow down instead of failing | Rate-limit headers on every answer, and JSON errors with a code and a message |
| Blocked destinations | A bad number in a prompt shouldn't dial an expensive line | Premium-rate numbers such as 900 and 976, and numbers outside the US and Canada, are refused |
Four ways an agent can pay for a fax
Payment decides whether an agent can finish a fax without a person. Fax services that list agent access in their own docs and in MCP directories, as of November 2026, use four approaches, and several offer more than one.
| How the agent pays | What has to happen first | Can the agent finish alone? |
|---|---|---|
| An account on a paid plan | A person signs up for a paid plan and approves access with OAuth in a browser, and an access token may need a higher plan | Yes, once a person has approved access |
| An API key | The key likely comes from an account with the service, and one service lists a free sandbox key for tests | Yes, once the agent has a key |
| A checkout link for each fax | Nothing; the agent gets a payment link back | No, in this mode a person opens the link and pays |
| A payment inside the request, such as x402 | A wallet the agent can sign from, holding USDC | Yes, with no account at the fax service |
FaxFair takes a payment inside the request with x402, and it also sells a prepaid key that a person funds by card.
Limits to plan around
A fax through the FaxFair API can have up to 100 pages, and the PDF can be up to 40 MB. It can go to a fax number in the United States or Canada, including US territories. Each destination number can receive a limited number of agent faxes a day, and callers are rate limited. When the limit is hit, the 429 answer carries a Retry-After header in seconds.
Anyone who has a fax id can read that fax's status, so the id belongs in private storage, not in a public log. FaxFair deletes the PDF from its servers once the fax is delivered or fails.
If you use an AI assistant
For a person chatting with an AI assistant, FaxFair runs a separate, read-only connector at https://api.faxfair.com/connector/mcp. It prices a fax, finds FaxFair guides and returns a faxfair.com link with the fax number filled in. The person uploads the pages and pays on the website, and the connector never sends a fax or takes a payment. To send one fax from a browser, see How to send a one-time fax.
Ready to connect an agent? The agent docs list the fields, headers and error format for both the MCP tools and the HTTP routes.
Read the agent docsQuestions
How do you send a fax with an API?
Send the fax number and a PDF to the API, pay, then check the status until it says delivered or failed. With FaxFair that is POST /v1/agent/faxes at https://api.faxfair.com with a pdf_url or a file upload, paid with a prepaid API key or USDC on Base, then GET /v1/agent/faxes/{id}.
Can an AI agent send a fax?
Yes. An agent can call a fax API over HTTP or through an MCP server. The FaxFair agent API takes a link to a PDF and a US or Canadian fax number, sends the fax and reports whether it was delivered or failed.
How much does it cost to send a fax with the FaxFair API?
As of November 2026, a fax of up to 40 pages costs $2.49 and a fax of 41 to 100 pages costs $6.99, the same prices as on faxfair.com. Priority costs twice that, $4.98 or $13.98. There is no monthly fee.
Does an AI agent need an account or API key to send a fax?
Not with FaxFair. An agent with a USDC wallet on Base can pay for one fax in the request itself, with no account. A prepaid API key is the other way to pay, funded by card, with a smallest top-up of $5.
What is x402?
x402 is an open payment standard that lets AI agents and APIs pay per request over HTTP. The server answers a request with HTTP 402 and the price, and the client signs a payment and sends the same request again with the payment attached.
Sources
All read on November 15, 2026.
- FaxFair, "Send a fax from an AI agent"
- FaxFair, "Fax API"
- Model Context Protocol, "Transports" (specification 2025-06-18)
- x402, "x402 - The internet-native payment protocol"
- Fax.Plus, "Fax.Plus MCP Server"
- MCPBundles, "Fax for Agents" listing
- mcpservers.org, "SendThisFax" listing
- mcpservers.org, "Faxer" listing