A Timerise productInboxParse: your inbox as an API for AI
Connect a Gmail or IMAP mailbox and get every email back as clean Markdown, structured JSON, and AI-generated labels and summaries. Query it from your code over a REST API, from your AI assistant over MCP (Model Context Protocol), or react to new mail with webhooks.
Free plan: 500 emails a month, no credit card required.
Your inbox
- ANAnna NowakInvoice 2041 for September
- BBBooking botTable for 4 moved to Friday
- MEMark EvansRe: demo next week?
Your agent reads
{
"from": "anna@studio-nova.pl",
"subject": "Invoice 2041 for September",
"labels": ["invoice", "finance"],
"summary": "Invoice for €420, due 15 October.",
"markdown": "Hi, please find attached…"
}- 500
- Free emails a month
- $49
- Developer plan a month
- 3
- Search modes
- EU
- Data processed by default
Why it exists
Why does a booking studio build an email API?
At Timerise we build AI-powered booking and reservation software. A large part of real-world scheduling still happens over email. Requests, confirmations, changes, and cancellations arrive as messy HTML threads that are hard to feed to an LLM (large language model).
We built InboxParse to solve that for ourselves and then opened it up as a standalone developer platform. It does for email what a web scraping API does for websites: it turns unstructured messages into data that software and AI agents can use.
How it works
How does a mailbox become an API?
- 1
Connect a mailbox
Sign in with Google for Gmail, or add any IMAP account. Credentials for IMAP are stored encrypted.
- 2
InboxParse syncs and normalizes
New messages are pulled in, HTML is converted to Markdown an LLM can read, and threads are grouped.
- 3
AI processing
Each email is labeled and summarized, and contacts are extracted from the conversation.
- 4
Use the data
Read it through the REST API, search it, let an AI assistant work with it over MCP, or receive webhooks when something happens.
What you get
What can you build on this email API?
REST API built for developers
A versioned API at /api/v1/ with API key authentication. Endpoints cover emails, threads, search, mailboxes, labels, contacts, webhooks, and usage. Every email comes back as structured JSON, as Markdown ready for an LLM prompt, or as the original message.
fullmarkdownrawSearch that understands meaning
Search across all connected mailboxes, so you can find “the email where the client asked to move the meeting” without guessing the exact words.
fulltextsemantichybridMCP server for AI assistants
Assistants such as Claude or Cursor can list, read, and search emails and threads, manage labels and webhooks, and check usage directly.
@inboxparse/mcpWebhooks
A signed HTTP callback (HMAC) when an event happens. Failed deliveries are retried automatically.
email.receivedemail.ai_processedemail.sentmailbox.syncedmailbox.errorContacts extracted from your email
People and companies mentioned in your threads are collected into a searchable contact list you can query or export to CSV.
Developer console
Manage mailboxes, API keys, labels, webhooks, and team members, try requests in an interactive playground, and track usage against your plan.
Use cases
What do people use it for?
AI agents that act on email
Give an agent read and reply access to a mailbox without writing Gmail or IMAP integration code.
Email RAG
Feed Markdown threads and semantic search into a retrieval-augmented generation (RAG) pipeline.
Lead extraction
Pull contacts and intent out of inbound sales email.
Support triage
Label and summarize incoming support requests and route them by webhook.
Operations alerts
Turn automated notification emails into structured events for your own systems.
Booking and scheduling workflows
Detect reservation requests, changes, and cancellations in email and hand them to a scheduling system such as Timerise.
Pricing
What does it cost?
Pricing is based on emails processed per month. Workspaces, mailboxes, and API calls are safety limits.
| Plan | Price / month | Emails / month | Mailboxes | Workspaces | API calls / month | Archive backfill |
|---|---|---|---|---|---|---|
| Free | $0 | 500 | 10 | 1 | 10,000 | No |
| Developer | $49 | 5,000 | 1,000 | 10 | 50,000 | No |
| Growth | $149 | 50,000 | 10,000 | 100 | 500,000 | Yes |
| Scale | $499 | 250,000 | Unlimited | Unlimited | Unlimited | Yes |
- Additional emails beyond the plan: $5 per 1,000.
Security and privacy
Where does my email data go?
- Data processed within the EU by default
- GDPR-aligned, with a standard Data Processing Agreement (DPA) available
- Hosted on Vercel and Supabase, with row-level security in the database
- Two-factor authentication (TOTP) for console accounts
- Published subprocessor list, security page, and acceptable use policy on inboxparse.com
FAQ
What do people ask?
Yes. InboxParse is developed, owned, and operated by Timerise Sp. z o.o., the company behind the Timerise booking platform.
Gmail (via Google sign-in) and any mailbox that supports IMAP.
No. The Free plan includes 500 emails per month.
Yes, through the InboxParse MCP server. It works with MCP-compatible clients such as Claude and Cursor.
Within the EU by default. Some subprocessors may process limited data outside the EEA; the full list is on the InboxParse subprocessors page.
Yes. InboxParse webhooks and API can feed booking-related emails into Timerise or any other scheduling system. There is no built-in, one-click integration today.
Get started
Turn your inbox into an API in minutes
Connect a mailbox, grab an API key, and make your first request.
The company
Who runs InboxParse?
InboxParse is owned and operated by Timerise Sp. z o.o. in Wrocław, Poland. Timerise develops the product and runs the service.
Timerise Sp. z o.o.
ul. Księcia Witolda 49/15, 50-202 Wrocław, Poland
- KRS
- 0000895019
- NIP
- 8971890756
- EU VAT
- PL8971890756
- hello@inboxparse.com