Developer Preview Β· Private Beta Β· Early Access Open

Ship fax in hours,
not weeks.

The only fax API with AI diagnostics built in. FaxDr tells you exactly why a fax failed β€” carrier mismatch, T.38 rejection, SIP timeout β€” before your customer ever calls support.

No spam, ever. Unsubscribe in one click.

Send a fax
$ curl -X POST api.faxdr.io/v1/send \
  -H "X-FaxDr-Api-Key: faxdr_sk_live_..."
  -d '{"to": "+16165551234",
     "pdf_url": "https://..."}'

# β†’ { "fax_id": "fx_9k2m...",
  "status": "queued" }
AI diagnose failure
$ curl api.faxdr.io/v1/faxes/
       fx_9k2m/diagnose

# β†’ {
  "root_cause": "T.38 rejected",
  "fix": "Use G.711 passthrough",
  "confidence": 0.94
}
Powered by Gemini 2.5 Flash
Sub-50msWebhook Delivery
99.95%SLA Target
48hPHI Auto-Delete
FreePoC API Testing

"We spent 3 hours on a 4-way conference call with AT&T, the receiver's IT team, and their carrier. Verdict: inconclusive." β€” That's the status quo FaxDr replaces.

πŸ”΄
The Problem We're Solving
Real scenario from healthcare telecom

FaxDr tries 4 different carrier routes in 2 minutes, delivers the fax, and hands you a diagnostic package showing exactly which hop was broken. No hold music required.

🟒
The FaxDr Solution
Multi-Carrier Route Discovery
Built onHL7 FHIR CompatibleGCP Healthcare APIHIPAA CompliantTelnyx PoweredStripe Billing

How It Works

Three steps to production fax

1
πŸ”’

Provision

Get a dedicated fax number in seconds. Search by state and city, provision with one API call.

2
πŸ“„

Send & Receive

Send PDFs via API, receive inbound faxes via webhook. Real-time status updates for every page.

3
🧠

AI Diagnoses

When faxes fail, Gemini AI analyzes the SIP trace and tells you exactly why β€” carrier mismatch, codec rejection, T.38 negotiation failure.

Features

Everything you need to ship fax

Production-grade infrastructure so you can focus on your product, not your fax stack.

🧠

AI-Powered Diagnostics

Gemini 2.5 Flash analyzes telecom traces in seconds. Get root cause analysis, not just error codes.

⚑

Sub-50ms Webhook Ingestion

Decoupled Pub/Sub architecture ensures 100% webhook resilience. Never miss an inbound fax.

πŸ“„

Send & Receive API

One API to send PDFs, receive inbound faxes, and track delivery status. E.164 numbers, any carrier.

πŸ”Œ

Outbound Webhooks

Real-time push notifications with HMAC-SHA256 signatures. Stripe-style verification.

πŸ“Š

Usage & Billing API

Metered billing via Stripe. Track pages, overages, and invoices programmatically.

πŸ”’

Number Management

Search, provision, release, and reclaim fax numbers via API. 30-day grace period on releases.

Multi-Carrier Route Discovery

GPS for fax. We find the detour.

When a fax fails between two carriers, the telecom route is blocked β€” like road construction with no detour sign. FaxDr tries different carrier routes until one gets through, then tells you exactly which road was blocked and why.

Without FaxDr

3-4 hours. Verdict: β€œinconclusive.”

  1. 1Fax fails. Staff notices hours later β€” or when the receiving clinic calls asking "where's the referral?"
  2. 2You open a ticket with your fax provider. Generic error: "Communication Error."
  3. 3You call AT&T. 45 minutes on hold. They say "it's the receiving carrier."
  4. 4Spectrum says "it's AT&T's problem." The blame game begins.
  5. 5You get the fax software vendor on the phone. They say "it's a carrier issue."
  6. 64-way conference call: AT&T, receiver's IT, their carrier, software vendor. Everyone points fingers.

Result

3-4 hours of engineer time burned. Verdict: β€œWe don't know.” Meanwhile, every fax to that destination has been failing silently.

With FaxDr Relay

~2 minutes. Fax delivered. Root cause found.

❌AT&T β†’ Spectrumpcap capturedFAIL
❌Bandwidth β†’ Spectrumpcap capturedFAIL
❌Vonage β†’ Spectrumpcap capturedFAIL
βœ…Lumen β†’ Spectrumpcap capturedDELIVERED

AI Diagnostic Package

Root cause: AT&T's intermediate gateway is stripping T.38 headers on routes to Spectrum. All pcaps attached. Working route: Lumen β†’ Spectrum. Confidence: 96%.

3-4 hrs

Traditional troubleshooting time

~2 min

FaxDr route discovery + delivery

$680+

Cost per incident (engineer time)

$0

Engineer hours with FaxDr Relay

Every attempt is a diagnostic.

Each relay attempt captures a full SIP trace and pcap. The AI analyzes all of them together β€” triangulating the exact point of failure from multiple carrier vantage points. Something no single-carrier provider can do.

πŸ”

Carrier Lookup

Instantly identifies the destination's carrier and line type. FaxDr knows which routes historically work for AT&T β†’ Spectrum, Comcast β†’ Lumen, and thousands of other combinations.

🧠

AI Root Cause Analysis

Gemini 2.5 Flash analyzes the SIP traces across all relay attempts. Root cause in plain English β€” not β€œlineError: 53” but β€œT.38 re-INVITE rejected at hop 3.”

πŸ“¦

Diagnostic Package

Full report with all pcaps, SIP traces, AI analysis, and the recommended permanent fix. Delivered via webhook and viewable in the portal. Verify independently if you want.

πŸ“ˆ

Route Intelligence

Every fax builds a smarter route table. Over time, FaxDr predicts which carrier route will succeed before trying β€” skipping known-bad paths entirely. It gets smarter with every fax.

Use Cases

Built for your stack

Whether you're wiring up an EHR, automating a pharmacy queue, or consolidating fax servers across a clinic portfolio β€” FaxDr has an integration pattern for you.

Your EHR handles data.
FaxDr handles the fax.

The problem

HL7/FHIR pipelines move in real time. Referrals that arrive by fax sit in a queue. Staff manually sort, route, and re-enter data β€” creating delays, errors, and missed appointments.

The FaxDr solution

FaxDr webhooks fire in under 50ms. Wire inbound referral faxes directly into your HL7 ADT feed or FHIR DocumentReference workflow. No polling, no queues, no manual sorting.

  • < 50ms webhook delivery
  • HL7 v2 & FHIR R4 compatible
  • Inbound OCR available via webhook
Read the EHR integration guide β†’
Python Β· FaxDr SDK
# Receive a referral fax and push to your FHIR endpoint
@app.post("/webhooks/faxdr")
def handle_inbound_fax(event: FaxEvent):
    if event.type == "fax.received":
        # Signed URL to download PDF β€” never stores PHI raw
        pdf_url = event.data["pdf_signed_url"]
        
        # Push to your EHR intake pipeline
        fhir_client.create_document_reference(
            content_url=pdf_url,
            category="referral",
            patient_id=extract_patient_id(pdf_url)
        )

Pricing

Simple, transparent pricing

Pricing below reflects our Q3 2026 launch rates. Join the waitlist for early access β€” founding members get 3 months free.

πŸ’‘ The average legacy fax server costs $18,000+/year in hardware, licensing, and IT. FaxDr Enterprise: $11,988/year.
Best Value

Growth

$299/mo
  • βœ“5,000 pages included
  • βœ“$0.04/page thereafter
  • βœ“AI failure diagnostics
  • βœ“Outbound webhooks (HMAC)
  • βœ“REST API + SDKs
  • βœ“Community support
Join the Waitlist

Founding members get 3 months free

Enterprise

$999/mo
  • βœ“20,000+ pages included
  • βœ“Everything in Growth
  • βœ“Signed BAA for HIPAA
  • βœ“Custom data retention
  • βœ“SLA guarantee (99.95%)
  • βœ“Dedicated Slack + 4h SLA
Join the Waitlist

BAA on Enterprise launch Β· Q3 2026

Pricing subject to change before launch. Fax PDFs auto-delete after 48h.

Security

Built for healthcare compliance

πŸ”’

HIPAA Ready

Signed BAA available. PHI encrypted at rest and in transit.

πŸ›‘οΈ

SOC II Architecture

Immutable audit trails, timing-safe auth, zero PHI in logs.

⏱️

48-Hour Auto-Delete

Fax PDFs auto-purge from storage. Private bucket, signed URLs only.

βœ…

Ed25519 Webhooks

Every inbound event cryptographically verified. 5-minute replay window.

FAQ

Everything you need to know

HIPAA buyers have tough questions. We have direct answers.

Yes. Enterprise plan customers receive a signed BAA automatically during onboarding. BAA is available within 24 hours of upgrade. Our BAA covers all data processing activities and meets HIPAA Subpart C requirements.

Fax PDFs are stored in a private GCS bucket with signed-URL-only access and auto-purge after 48 hours. We never log PHI in application or observability pipelines. Storage region: us-central1 (Iowa, USA). All data at rest is AES-256 encrypted.

Every failed fax returns a detailed error code plus AI-generated root cause analysis via the /diagnose endpoint. You'll get the exact failure mode (T.38 negotiation, carrier timeout, codec rejection) and a specific recommended fix. You can retry immediately via API or configure auto-retry logic in your webhook handler.

99.95% monthly uptime SLA with financial credits for violations. You get a dedicated Slack channel and a 4-hour response time for P1 incidents. We publish a live status page at status.faxdr.io.

Number porting is available on the Enterprise plan. We support all major US carriers. Provisioning new numbers takes under 30 seconds via API β€” search by area code, state, or city prefix.

Our architecture follows SOC 2 Type II principles: immutable audit trails, timing-safe authentication, and zero PHI in observability pipelines. We are actively pursuing formal SOC 2 Type II certification, expected Q3 2026. A security architecture review is available on request for Enterprise prospects.

Three key differences: (1) AI diagnostics β€” we're the only fax API that tells you WHY a fax failed and how to fix it, not just that it did. (2) Developer-first design β€” Stripe-style HMAC-signed webhooks, typed SDKs, OpenAPI spec, and an MCP server for AI tooling. (3) HIPAA-native architecture β€” compliance is built into the data model, not bolted on after.

Growth plan ($299/mo): $0.04/page after 5,000 pages. Enterprise plan ($999/mo): custom overage rates negotiated at contract time. You'll receive an automated alert at 80% of your monthly page limit so you're never surprised.

Still have questions?

Talk to our team β†’