# Point your coding agent here

> Point your coding agent at Email Fast: llms.txt, markdown mirrors of every page, an OpenAPI spec, sandbox keys, and an MCP server arming at launch.

Canonical: https://emailfast.dev/agents

## The reading list for your agent

| Resource | URL |
|---|---|
| Site index for LLMs | [/llms.txt](/llms.txt) |
| Full corpus, one file | [/llms-full.txt](/llms-full.txt) |
| Any page as markdown | append `.md` to its URL — e.g. `/developers.md` |
| OpenAPI specification | [/openapi.yaml](/openapi.yaml) |
| Machine-readable pricing | [/.well-known/pricing.txt](/.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 is `Authorization: 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_key` on 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](/docs/quickstart-node), tell us —
**hello@emailfast.dev** — broken agent-docs are bugs here, not curiosities.

## 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.