MailFrame
mailframe.ai
- Free plan
- Web
- API
What MailFrame is
MailFrame is an API for developers who need to turn incoming email into typed JSON checked against a schema. A request can include raw RFC 822 MIME or plain-text email-like input along with a JSON Schema, and the service returns validated JSON synchronously. Developers can send an inline schema without registering or choose from a library covering receipts and orders, invoices, travel bookings, shipping notices, and GitHub notifications. Signed HMAC-SHA256 webhooks provide retries, attempt history, a dead-letter queue, and replay for delivery to downstream systems that accept webhooks. The current API accepts email content only; PDF and image input are planned. MailFrame says it keeps raw email only as long as needed for delivery and debugging, does not sell or share customer data, and stores API keys in hashed form. It is in limited early access, with developers onboarded in weekly batches. The Free plan includes 100 parse operations per month with no credit card required. Paid plans start at $19 per month. SOC 2 Type II is on the roadmap, and MailFrame says it is not yet HIPAA-eligible as a Business Associate.
Who it suits
MailFrame suits developers integrating inbound document email into their own services, especially when those services can receive webhook deliveries. It is less suited to workflows that need PDF or image parsing now.
Good to know, and what to watch
- Inline JSON Schemas can be used without registration
- Returns schema-validated JSON synchronously
- Webhook delivery includes retries and replay
- Free plan includes 100 monthly parse operations
- PDF and image input are planned, not available now
- Limited early access uses weekly developer onboarding
- Not yet HIPAA-eligible as a Business Associate
Plans
Every plan and priceEnterprise
Free
Indie
Startup
Free plan
Getting started
- Visit https://mailframe.ai/.
- Use the API platform to send raw MIME or plain-text email-like input with a JSON Schema.
- Provide an inline schema or select a suitable prebuilt schema.
- Choose a plan: Free is $0 per month, with paid plans starting at $19 per month.
- Configure webhook delivery if results need to reach a downstream system.
Limits to check
Free includes 100 parse operations per month and one active schema. Indie costs $19 per month and includes 500 parse operations and five active schemas; further documents cost $0.038 each. PDF and image input and confidence scoring appear as planned features on Startup, not current API inputs.
The Club's review
Overview
MailFrame is an API for developers who need structured data from inbound email in their own application. It is best suited to teams comfortable building around schemas and webhooks. Its email-focused approach is useful, but it does not yet handle attachments.
Key features
Schema-based parsing
Send raw RFC 822 MIME or plain-text email-like input with a JSON Schema, and MailFrame returns synchronously validated JSON. Inline schemas require no registration, which makes it easier to match output to an application’s data model without a separate schema setup step. Prebuilt schemas span receipts and orders from Stripe and Shopify, PayPal and Amazon receipts, Apple App Store and Google Play receipts, GitHub notifications, invoices, travel bookings, and shipping notifications. That breadth can save setup for common email formats; teams with unusual inputs can supply their own schema.
Webhook delivery
Signed HMAC-SHA256 webhook delivery includes retries, attempt history, a dead-letter queue, and replay. These controls give developers ways to inspect failed deliveries and resend them, provided their downstream system accepts webhooks. This is an integration component rather than a general-purpose inbox or document-processing suite.
Input, security, and compliance
The current API accepts email content rather than PDF or image input; both attachment parsing and OCR extraction are unavailable, while PDF and image support is planned. This makes MailFrame a poor fit when documents arrive as attachments. MailFrame says it retains raw email only as long as needed to deliver the response and surface debugging, does not sell or share customer data, and stores API keys as hashes that cannot be recovered as raw keys. SOC 2 Type II is on the roadmap, and MailFrame is not yet HIPAA-eligible as a Business Associate, so it is not suitable for workloads that require that eligibility.
Pricing
MailFrame has a free tier and paid plans billed monthly, with paid plans starting at $19/mo. The Free plan costs nothing and includes 100 parse operations per month, one active schema, webhook delivery, community support, and no credit-card requirement. It is a low-commitment way to validate a workflow, but the single-schema cap and quota constrain ongoing use. The maker describes it as a trial tier for validating the product; no separate trial length is given.
Indie costs $19 a month for 500 parse operations, five active schemas, signed webhook delivery, email support, schema versioning, and $0.038 per document after the quota. It fits a small integration that needs signed delivery and a few schema types; the operation cap makes it less suitable for higher-volume processing. Startup costs $49 a month for 5,000 parse operations, unlimited schemas, API key scoping, priority support, and $0.0098 per document after. PDF and image input and confidence scoring are planned rather than current features, so the plan’s value today rests on its higher quota, schema capacity, and key scoping.
Scale costs $149 a month for 50,000 parse operations, unlimited schemas, cache hits included, custom webhook rate limits, and $0.003 per document after. Async and batch API are planned, and the uptime target applies post-GA, so buyers needing those capabilities now should not count on them. Enterprise has custom pricing for 100k+ parse operations per month, with custom volume pricing, dedicated infrastructure, custom SLAs, an account manager, and SSO / SAML; SOC 2 remains on the roadmap. It is aimed at larger deployments, but buyers needing current SOC 2 coverage should look elsewhere.
Every paid plan specifies a per-document overage price. The published monthly email limit is 500 emails per month; readers should distinguish that stated email limit from plan quotas expressed in parse operations.
Platforms
MailFrame is offered via API and web. Its API-first model and webhook delivery suit developers integrating parsing into their services, rather than users seeking a standalone desktop or mobile workflow.
Who it's for
MailFrame suits application developers who receive useful data through email and want validated, schema-shaped results delivered into webhook-compatible systems. It is a stronger match for teams whose inputs are email bodies and who can work within the operation and schema limits of their chosen plan. Teams that rely on attachments, OCR, HIPAA eligibility, or generally available service should weigh those gaps and its limited early-access onboarding, which proceeds in weekly batches.
Pros and cons
- Pro: Inline JSON Schemas and a broad prebuilt library let developers shape outputs for common receipts, orders, notifications, invoices, bookings, and shipping messages.
- Pro: Signed webhook delivery with retries, attempt history, dead-letter handling, and replay gives integrations useful failure-management controls.
- Pro: The free tier provides 100 parse operations monthly without a credit card, making initial workflow validation possible without a paid commitment.
- Con: Current input is limited to raw MIME and plain-text email-like content; there is no attachment parsing or OCR.
- Con: Free allows only one active schema, and paid operation quotas can be exceeded only at stated per-document overage rates.
- Con: Limited early access, SOC 2 still on the roadmap, and no HIPAA eligibility restrict adoption for some production and regulated environments.
Alternatives
For a wider comparison, browse Email Parsing Software. Choose Parserr if a free allowance of 15 emails per month, one inbox, unlimited parsing rules and integrations, plus Zapier and Microsoft Flow, better matches the workflow. Parsio Receipt OCR is an alternative with a free tier of 30 credits per month, 30-day data retention, and one user. Consider DigiParser for a paid plan starting at $14/month for 100 payslips, or enterprise pricing for 1,000+ documents monthly. Parseur offers a free plan of up to 20 pages per month, one user, 90-day retention, and unlimited mailboxes and extracted fields. noima offers 10 documents as a one-time free allowance with 30-day retention, followed by a Starter tier at €12 per month for 150 documents and 60-day retention. MailParse is a paid alternative whose Starter plan costs $24 a month, billed yearly, for 100 emails monthly and Excel, CSV, and JSON exports, custom fields, an IMAP mailbox, and saved templates. Parsli is another option for readers comparing email-parsing services. Airparser offers a 30-day trial with 20 credits per month, all features included, and 30-day document retention.
Verdict
MailFrame is a compelling fit for developers who want schema-validated email data and dependable webhook delivery without building that parsing layer themselves. Its inline schemas, useful prebuilt coverage, and delivery recovery controls are the main reasons to choose it. Look elsewhere if your inputs depend on attachments or OCR, you need HIPAA eligibility, or you cannot adopt a service still in limited early access.
The verdict
MailFrame provides a focused route from raw email to schema-validated JSON, with webhook delivery controls for downstream systems. Its current input limits and early-access availability are important considerations for adoption.
Questions people ask
Is there a free plan?
Yes. Free costs $0 per month and includes 100 parse operations per month, one active schema, webhook delivery and community support; no credit card is required.
How much do paid plans cost?
Indie is $19 per month, Startup is $49 per month and Scale is $149 per month. Enterprise pricing is custom.
What input can MailFrame parse?
The current API accepts raw RFC 822 MIME and plain-text email-like input. PDF and image input are planned.
Can I use my own schema?
Yes. A JSON Schema can be sent inline without a registration step, or you can choose from the prebuilt schema library.
What platforms does MailFrame support?
The listed platforms are API and web.
Is MailFrame HIPAA-eligible?
MailFrame says it is not yet HIPAA-eligible as a Business Associate. SOC 2 Type II is on its roadmap.
What the maker publishes
- Accepted input
- The supported input is raw RFC 822 MIME or plain-text email-like content, while PDF and image parsing are planned. source
- API authentication
- Requests use bearer tokens over HTTPS, with environment-scoped keys that can be created, scoped, rotated, and revoked. source
- API endpoint
- The primary parser is POST /v1/parse and returns typed JSON synchronously in the same HTTP response. source
- API error handling
- The API documents 400, 401, 422, 429, and 5xx response meanings and JSON error envelopes. source
- API examples
- The documentation supplies curl, TypeScript, and Python examples for every documented endpoint. source
- API key security
- API keys are stored hashed, so the raw key cannot be recovered from MailFrame's records. source
- Audience
- MailFrame says it is for app developers integrating inbound document email into their own service. source
- Availability
- MailFrame is in limited early access and says it is onboarding developers in weekly batches. source
- Chrome data disclosure
- The listing declares handling of personally identifiable information, authentication information, personal communications, and website content. source
- Chrome developer status
- The Chrome developer is marked as a non-trader and states that disclosed data is not sold or used for unrelated purposes. source
- Chrome extension features
- The listing describes Gmail summaries, multilingual output, order and invoice extraction with CSV export, calendar links, focus reading, and daily briefs. source
- Chrome listing identity
- The Chrome listing is a Gmail extension whose developer website and support address use mailframe.org rather than mailframe.ai. source
- Chrome listing users
- The Chrome listing shows 6 users, version 1.0.1, and an update date of June 11, 2026. source
- Chrome plan limits
- The extension listing advertises Free at 30 summaries monthly, Pro at 1,000 summaries monthly, and a Business tier for higher-volume extraction. source
- Chrome privacy claim
- The extension says it processes only the active thread on demand, does not scan the mailbox in the background, and does not store email content. source
- Compliance
- SOC 2 Type II is on the roadmap, and MailFrame says it is not yet HIPAA-eligible as a Business Associate. source
- Compliance status
- SOC 2 Type II is on the roadmap and MailFrame is not currently HIPAA-eligible as a Business Associate. source
- Confidence scoring
- The product returns an overall confidence value and low-confidence field information for parses. source
- Credential protection
- API keys are stored hashed, while webhook secrets are shown once and stored encrypted. source
- Custom schemas
- Users can provide an inline JSON Schema without a registration step. source
- Custom schemas
- Clients may send an inline JSON Schema without registering it first. source
- Data handling
- MailFrame says it retains raw email content for the minimum time needed to deliver the response and surface debugging, and does not sell or share customer data. source
- Data retention
- MailFrame says raw email is retained only as long as needed to return the response and support debugging, and customer data is not sold or shared. source
- Delivery
- MailFrame supports signed HMAC-SHA256 webhook delivery with retries, attempt history, a dead-letter queue, and replay. source
Checked against the maker's pages on 15 Oct 2026.