Resend-style fax delivery

Fax API for agents that need a receipt.

One endpoint for regulated document delivery: idempotent sends, dry-run validation, delivery webhooks, OpenAPI, and llms.txt built in from day one.

Read the docs See pricing

AgentFax delivery console showing API request and fax status timeline — Agent-safe fax transmission with dry runs, status events, and replay protection.

Quickstart

Send a dry-run before the real fax.

Agents can validate phone numbers, file URLs, request shape, and idempotency before spending money or transmitting sensitive documents.

curl https://agentfax-api.scshome.workers.dev/v1/faxes \
  -H "Authorization: Bearer afx_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: contract-8921-v1" \
  -d '{
    "to": "+13125550123",
    "media_url": "https://example.com/contracts/8921.pdf",
    "client_reference": "contract-8921",
    "dry_run": true
  }'

Idempotency

Retries without duplicate faxes

Every send can carry a stable idempotency key so tool retries return the original fax object.

Dry runs

Validate before transmit

Agents can prove request validity before sending regulated, expensive, or irreversible documents.

Events

Delivery state as data

Fax state is normalized into `queued`, `sending`, `delivered`, `failed`, and `canceled` events.

AI docs

OpenAPI and llms.txt

Machines get small, explicit docs. Humans get a direct quickstart, error model, and webhook guide.

SEO wedge

Own the long-tail around fax automation.

fax api fax api for ai agents fax delivery webhook idempotent fax send api fax api openapi schema