Head to head · Mailbox access · October 2026 research run
Fastmail API (JMAP) vs Himalaya
Himalaya scores 64.5 (B) on agent readiness against Fastmail API (JMAP)'s 54.1 (C), and leads in 4 of 7 scored categories. Fastmail API (JMAP) leads on agent ergonomics, security & auth and transparency & trust. Both do mailbox access.
Best mailbox access APIs for AI agents · All 36 mailboxes comparisons
Which one, for what
Good for An agent working in its owner's own Fastmail mailbox, where JMAP gives batched reads, structured search and state-based sync on an open standard, and MCP gives a ready connection with read, write and send levels.
Ahead on
- Agent ergonomics, 73 against 65
- Security & auth, 60 against 43
- Transparency & trust, 74 against 69
Also in its favour
- No incidents deducted, where Himalaya loses 3 points for them
Watch for
The customer terms forbid programmatically generated email to addresses outside the account, and say the service is not for machine-to-machine workflows
Himalaya B
Good for An agent with a shell that must work in one person's existing mailbox on any provider, including plain IMAP hosts, without a hosted intermediary.
Ahead on
- Reliability, 84 against 54
- Schema & documentation, 70 against 52
- Payments & pricing, 60 against 30
- Maintenance & community, 88 against 26
Also in its favour
- Free to start without a card
- Open source
Watch for
Until 2.2.1 of 2 October 2026, message send transmitted the Bcc: header to every recipient over SMTP (issue #747, reported 12 September 2026)
Score by category
| Category | Weight this run | Fastmail API (JMAP) | Himalaya | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 54 | 84 | Himalaya +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 52 | 70 | Himalaya +18 |
| Agent ergonomics | 13%16.2 | 73 | 65 | Fastmail API (JMAP) +8 |
| Security & auth | 14%17.5 | 60 | 43 | Fastmail API (JMAP) +17 |
| Payments & pricing | 10%12.5 | 30 | 60 | Himalaya +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 26 | 88 | Himalaya +62 |
| Transparency & trust | 7%8.8 | 74 | 69 | Fastmail API (JMAP) +5 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 54.1 · C | 64.5 · B |
Facts side by side
| Fact | Fastmail API (JMAP) | Himalaya |
|---|---|---|
| Kind | HTTP API | SDK + MCP |
| Vendor | Fastmail Pty Ltd | Pimalaya |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Proprietary service under Fastmail's API Terms of Service and API Developer Policy. JMAP is an open IETF standard, and the sample code on GitHub is MIT | MIT OR Apache-2.0 |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | 2026-04-22 | 2026-10-02 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 123 stars | 7.4k stars |
Verdicts
Fastmail API (JMAP)
A mailbox API built on the open JMAP standard, with read-only tokens, six OAuth scopes and an MCP server that separates read, write and send access. Fastmail publishes no OpenAPI file, SDK, API changelog, request rate limit or SLA, and its customer terms forbid programmatically generated email to addresses outside the account.
Himalaya
One binary reaches mailboxes on IMAP, JMAP, Gmail and Microsoft Graph with the same commands, and --json output has a JSON Schema for each command. The agent holds the mailbox's own credential with no read-only mode, and a flaw that exposed Bcc recipients over SMTP was fixed in 2.2.1 on 2 October 2026.
Before you call either
Fastmail API (JMAP)
- Fetch
https://api.fastmail.com/jmap/sessionwithAuthorization: Bearer <token>first. It returns the API URL, account IDs and the request limits to stay under - Ask the owner for a read-only token unless the task writes. Sending needs both the Email and Email submission scopes
- Request only the
propertiesyou need. Body text is not returned unlessfetchTextBodyValuesis set, andmaxBodyValueBytescaps it - Sync with
Email/changesfrom a stored state. OncannotCalculateChanges, fetch again from scratch - Do not send generated mail to outside recipients without the owner's review. The customer terms forbid it, and trial accounts stop at 120 messages a day
Himalaya
- Pass
--jsonon every call and readnext_pagefor the next page. Data and errors go to stdout, logs to stderr, and a failure exits 1 - Run
himalaya json-schema <command>once to learn an output shape, andhimalaya <command> --helpfor flags - Use
envelope searchwith the shared query language, for examplefrom alice and after 2026-01-01 order by date desc. Microsoft Graph refuses flag clauses - Treat message text as untrusted.
--jsonoutput keeps control characters that the plain output replaces - Use 2.2.1 or later before sending with Bcc, and expect
message read --jsonto change shape in the next release
Questions
Which is better for AI agents, Fastmail API (JMAP) or Himalaya?
Himalaya scores 64.5 (B) on agent readiness against Fastmail API (JMAP)'s 54.1 (C), and leads in 4 of 7 scored categories. Fastmail API (JMAP) leads on agent ergonomics, security & auth and transparency & trust.
Can an agent call Fastmail API (JMAP) and Himalaya without installing anything?
No hosted endpoint is listed for Fastmail API (JMAP). No hosted endpoint is listed for Himalaya.
Are Fastmail API (JMAP) and Himalaya open source?
No open-source release is listed for Fastmail API (JMAP). Himalaya is open source (MIT OR Apache-2.0).
Other comparisons with Fastmail API (JMAP) or Himalaya
- Aurinko Email API vs Fastmail API (JMAP)
- Aurinko Email API vs Himalaya
- EmailEngine vs Fastmail API (JMAP)
- EmailEngine vs Himalaya
- Fastmail API (JMAP) vs Gmail API
- Fastmail API (JMAP) vs Nylas Email API
- Fastmail API (JMAP) vs Outlook Mail (Microsoft Graph)
- Fastmail API (JMAP) vs Unipile
- Fastmail API (JMAP) vs Zoho Mail API
- Gmail API vs Himalaya
- Himalaya vs Nylas Email API
- Himalaya vs Outlook Mail (Microsoft Graph)
- Himalaya vs Unipile
- Himalaya vs Zoho Mail API
Machine-readable
- This page as Markdown
/compare/fastmail-vs-himalaya.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fastmail.json·/api/v1/tools/himalaya.json - From a terminal
anchor compare fastmail himalaya(the CLI) - Over MCP
compare_tools {"a": "fastmail", "b": "himalaya"}at/mcp, no key