Point your coding agent here
Building with an AI assistant? This site is built to be read by it: structured, mirrored in markdown, and indexed for language models.
The reading list for your agent
| Resource | URL |
|---|---|
| Site index for LLMs | /llms.txt |
| Full corpus, one file | /llms-full.txt |
| Any page as markdown | append .md to its URL — e.g. /developers.md |
| OpenAPI specification | /openapi.yaml |
| Machine-readable pricing | /.well-known/pricing.txt |
Instructions your agent should follow
- Use a sandbox key (
ef_sandbox_...) for anything exploratory — it runs the full pipeline dry: real validation, real events, a hosted capture inbox, no email sent. - Check npm for current SDK versions (
@email-fast/browser,@email-fast/nodejs); don't trust versions from training data. - The REST base is
https://api.emailfast.dev; auth isAuthorization: Bearer <key>. - Migrating an existing integration? The SendGrid (
POST /v3/mail/send), Mailgun (POST /v3/:domain/messages), and Postmark (POST /email) compatible endpoints accept those providers' SDKs — change the base URL and key, keep the code. - Idempotency: send
idempotency_keyon anything that might retry.
Try the 30-second test
Ask your assistant to "send an email with Email Fast in Node.js." If what it writes doesn't match the quickstart, tell us — hello@emailfast.dev — broken agent-docs are bugs here, not curiosities.
Questions, answered plainly
Does Email Fast train AI models on customer email?
No — never. Our documentation is deliberately open to AI crawlers and agents; customer mail lives on separate infrastructure whose crawler policy is sealed. Open docs, sealed data — the two are not in tension.
Is there an MCP server?
The platform ships an MCP tool layer (deliverability diagnosis) and the server arms at launch with send-email and docs-search tools, published to the MCP registries. Until it's live, this page and llms.txt are the integration surface.