Run curl api.email and the site answers with plain text instead of HTML: a short guide to the API that fits in a terminal window. It is the fastest way to remember an endpoint, and it is what a coding agent sees when it explores the service from a shell.
curl api.emailThe response covers the essentials: the base URL https://api.email/v1, how to pass your key in the Authorization header, a complete POST /v1/emails example, how to add a domain with two CNAME records and how to receive email with an MX record and a route. It ends with links to the full documentation and to llms.txt.
Why plain text
Developers and agents increasingly start in a terminal. A browser page full of navigation and scripts is noise for a tool that only needs the facts, while a plain-text answer can be read by a person, piped into a file or pasted into an agent’s context. The same request with a browser user agent still gets the normal website.
A copy-paste quickstart
export API_EMAIL_KEY="ae_test_…"
curl https://api.email/v1/emails \
-H "Authorization: Bearer $API_EMAIL_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "Acme <[email protected]>", "to": "[email protected]", "subject": "Hello", "text": "Sent from my terminal."}'With a test key, the request is validated and returns an id, but nothing is delivered. Replace it with a live key once your domain is verified.
For agents
If you are asking an agent to integrate api.email, tell it to run curl api.email first, or to read https://api.email/llms.txt. Both give it the current endpoints and field names, which avoids guessed or outdated API calls.