Nurreo developer documentation
Everything a developer or an agent needs to integrate with Nurreo, the email and calendar provider on your own domain where agents are first-class operators.
Nurreo is at waitlist stage. One API is live today — the waitlist — and the mailbox surface below is specified but not yet shipped. This page says plainly which is which.
Live today
| Resource | URL | Format |
|---|---|---|
| Nurreo Waitlist API reference | /docs/api | HTML + Markdown |
| Nurreo OpenAPI 3.1 specification | /openapi.json | JSON |
| Nurreo agent guide (agent instructions) | /agent.md | Markdown |
| Nurreo llms.txt index | /llms.txt | Markdown |
| Sitemap | /sitemap.xml | XML |
Specified, not yet shipped
| Resource | URL |
|---|---|
| Nurreo CLI and MCP server reference | /docs/agents |
Authentication, capability grants, and webhooks are described on that page as planned behaviour. There is no mailbox API to call yet; the waitlist is the only endpoint that accepts requests.
Every page here speaks Markdown
Nurreo's site does Accept: content negotiation, per
acceptmarkdown.com. Ask any page for Markdown and you
get Markdown from the same URL:
curl -H 'Accept: text/markdown' https://nurreo.com/docs/api
HTML pages advertise their Markdown twin with a Link: <...>; rel="alternate"; type="text/markdown" header and a matching <link rel="alternate"> element.
Responses carry Vary: Accept, Accept-Encoding so caches never hand an agent the
HTML variant by mistake.
Conventions
- JSON in, JSON out. Every API response is
{"ok": true|false, ...}. - Real status codes. Nonexistent paths return
404with a Markdown body that points back here. Nurreo never answers a missing path with200. - CORS is open on
/api/*. Agents call Nurreo from anywhere; that is the pitch. - No bot wall. robots.txt allows every crawler and agent, and always will.
Contact
hello@nurreo.com — for API questions, integration help, or to tell us the docs are wrong.