sendfax.sh valid
SendFax.sh
Send real faxes over HTTP. One API call, paid per page with x402 or MPP (USDC) -- no account, no API key. Humans can send via Stripe Checkout.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://sendfax.sh/llms.txt
- llms-full.txt
- https://sendfax.sh/llms-full.txt
- Sections
- 2
- Links
- 17
- Size
- 4245 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Interface: a documented API or declared MCP endpoint an agent can call
- First seen
- 2026-10-27T13:27:43.586Z
- Last checked
- 2026-10-27T13:27:45.064Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:27:43.592Z. Cached copy · Source on sendfax.sh
# SendFax.sh
> Send real faxes over HTTP. One API call, paid per page with x402 or MPP (USDC) -- no account, no API key. Humans can send via Stripe Checkout.
SendFax.sh is a single-purpose service: send a fax. Agents call a paid HTTP API and settle per request in USDC over x402 or MPP; there are no accounts and no API keys, because the payment itself is the credential. Humans use a drag-and-drop page and pay with Stripe (Link, card, or crypto). Faxes are delivered via Telnyx Programmable Fax and are real-time: the PDF is streamed to the carrier and deleted after sending -- we never store your document. The carrier is HIPAA-compliant (real-time T.38, nothing stored on either end) and SOC 2 Type II, ISO 27001, PCI DSS and GDPR certified. There is no per-transaction minimum and no credit top-up: a one-page fax costs one page.
Pricing is $0.05 per page. On the agent rails (x402/MPP) there is no minimum; the human Stripe flow floors at Stripe's $0.50 minimum charge.
Destinations: SendFax currently delivers to the US, Canada, Mexico, and St. Pierre & Miquelon; a number outside those countries returns HTTP 422.
Support: support@sendfax.sh
## Docs
- [Quickstart](https://sendfax.sh/quickstart.md): send a fax in four steps, with the 402 payment handshake shown end to end.
- [Integration guides](https://sendfax.sh/guides/index.md): index of the platform guides -- every page has a markdown twin at /guides/{slug}.md.
- [HTTP wire format](https://sendfax.sh/guides/http.md): the language-agnostic protocol reference -- every request and response, the multipart shape, both 402 dialects verbatim, idempotent retry semantics, the status lifecycle, and the problem+json error table.
- [Paying with USDC](https://sendfax.sh/guides/usdc.md): the protocol-level guide -- full 402 anatomy, the exact-amount rule, Base + the USDC contract, direct-transfer settlement, refunds, end-to-end curl.
- [Paying with MPP](https://sendfax.sh/guides/mpp.md): the MPP dialect -- the WWW-Authenticate: Payment challenge decoded field by field, its relationship to x402, and what settles today.
- [Sending via curl](https://sendfax.sh/guides/curl.md): the no-dependency reference implementation -- 20 lines of bash for the wallet path, plus the Stripe Checkout path.
- [Sending with TypeScript](https://sendfax.sh/guides/typescript.md): the `sendfax` npm SDK end to end on Node 18+/Bun/Deno, a PaymentHandler wired to a local key with viem, and the plain-fetch version.
- [OpenAPI spec](https://sendfax.sh/openapi.json): OpenAPI 3.1 description of every endpoint, the 402 payment responses, and the schemas.
- [Authentication](https://sendfax.sh/auth.md): there is no auth -- payment is the credential (x402/MPP per request); humans use Stripe Checkout.
- [Agent skill](https://sendfax.sh/SKILL.md): a portable, paste-ready skill describing how to send a fax. Installable into any agent with `npx skills add DanielSinclair/sendfax.sh --skill sendfax -g`.
- [MCP server](https://mcp.sendfax.sh/mcp): remot
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| fax.plus | Fax.Plus | interface Healthcare APIs and SDKs +1 | US | 57 | ✓ | ||
| gotfreefax.com | GotFreeFax | transactional Communications | US | 55 | ✓ | ||
| ifaxapp.com | iFax: HIPAA-Compliant Fax | Send and Receive Faxes Online | transactional Communications Healthcare | US | 57 | ✓ | ||
| westfax.com | WestFax — HIPAA-compliant cloud fax | interface Communications | US | 52 | ✓ | ||
| markdown2pdf.ai | markdown2pdf.ai | interface AI and machine learning AI agents and MCP +1 | US | 48 | ✓ | ✓ | |
| efax.com | eFax | transactional Communications Business software | — | 65 | ✓ | ✓ | |
| mpp.dev | MPP — Machine Payments Protocol | interface Finance and payments APIs and SDKs +1 | US | 57 | ✓ | ✓ | |
| openpayments.dev | Open Payments | interface Finance and payments APIs and SDKs +1 | DE | 48 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=sendfax.sh · GET /v1/domain/sendfax.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage sendfax.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for sendfax.sh:
1. POST https://agentwebmap.com/v1/sites/sendfax.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://sendfax.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/sendfax.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/sendfax.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.