Parseur alternative

What a credit costs #

The counting rule is theirs and it is fair: an email is one credit however long it is, and a three-page PDF is three. That is honest metering for a product built around documents. It also means that if your workload is email bodies rather than PDFs, you are paying document prices for messages.

At the bottom of the curve the gap is stark — 100 emails a month costs €49 there and nothing here, because our free tier is 300 a month with no card and no expiry. At the top it narrows in relative terms but not in absolute ones: Parseur’s 10,000-page plan is €499; MailMint’s 25,000-email plan is $29.

What Parseur does better than us, today #

• It reads PDF and scanned documents. OCR, multi-page, page-counted. MailMint does not read attachment contents yet. If your data lives inside the attachment rather than the message, this page ends here and you should use Parseur.
• Its Table Field is mature. Variable-row tables in AI mode work well; the documented cap is 25 pages per document.
• Its n8n node is official and verified, published 21 August 2026. Ours was published in n8n’s verified registry on 1 September 2026 and works on n8n Cloud and self-hosted n8n.
• It has the integrations you would expect of a mature vendor — Zapier, Make, Power Automate, Google Sheets, Excel — and years of production use behind it. MailMint has an API, webhooks, polling and n8n.

That is not a courtesy paragraph. If any line in it is your requirement, buy Parseur.

Side by side #

Parseur figures from their pricing endpoint and their published OpenAPI 3.1 schema, read 29 August 2026, re-checked 30 August 2026. Scroll sideways on a narrow screen.

Per-field confidence, and why a document-level verdict is not the same thing #

Parseur tells you whether a document parsed. It does not tell you that the total is solid and the due_date is a guess. In practice that is the difference between routing a document and routing a field: with one verdict per document you either trust all eleven fields or review all eleven.

MailMint returns a confidence, a source and an evidence span per field, and sets needs_review on the message with flags naming which field caused it. The number is not the model’s self-report: it is computed from whether the quoted evidence is really a verbatim substring of the message, whether the rules layer and the model agreed independently, whether the invoice arithmetic reconciles, and whether the value coerced cleanly to its type. The model’s own opinion is one input, weighted least, and it can only lower a score.

The evidence span has a second use that is easy to miss: it is an audit trail. When someone asks in March why an invoice was booked at €1,180.50, the answer is the exact characters of the email that number was read from, kept alongside the value.

Schema over the API #

Parseur publishes a genuinely good REST API for documents — upload, fetch results, re-process. What it does not expose is the template: fields are defined by hand in their UI.

If you are building a product where each of your customers gets their own inbound address and their own field set, that difference is the whole integration. MailMint creates a mailbox and its schema over the API, and PATCH /v1/mailboxes/:id changes the fields later without touching a UI:

curl -X POST https://mailmint.app.mintapis.com/v1/mailboxes \
  -H "Authorization: Bearer $MAILMINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "acme-invoices",
        "schema": [ { "name": "total", "type": "number", "description": "grand total including tax" } ],
        "webhook_url": "https://your.app/hooks/mailmint" }'

The volume curve, plainly #

Take 1,000 emails a month, no attachments. Parseur Starter is €129. MailMint Starter is $9 and has 4,000 parses left over. Take 100 a month: €49 against $0. Take 3,000 a month: €269 against $9. These are list prices from both vendors on the same day, for email bodies only — the workload where a page-based credit is least kind to you and where our per-email price is most honest about what we actually do.

The same job, here #

Stateless, nothing stored, no mailbox needed:

curl -X POST https://mailmint.app.mintapis.com/v1/parse \
  -H "Authorization: Bearer $MAILMINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Order 8841 shipped",
    "text": "Your order 8841 shipped on 28 Aug 2026 via DHL, tracking JD014600003922379820.",
    "schema": [
      { "name": "order_id", "type": "string", "description": "the order number" },
      { "name": "carrier",  "type": "string", "description": "the shipping carrier" },
      { "name": "tracking", "type": "string", "description": "the tracking number" },
      { "name": "shipped_on", "type": "date", "description": "the date it shipped" }
    ]
  }'

When you should stay on Parseur #

• Your documents are PDFs, scanned or otherwise. This is the clearest line between the two products and it is not close today.
• You need n8n Cloud without community nodes, or Zapier, Make or Power Automate as a first-class integration.
• You need a vendor with a track record. Parseur has years of production customers. MailMint has none yet, and we are not going to imply otherwise.

What we cannot claim #

MailMint has paying customers, but no customer logo, testimonial or case study is quoted without permission, and there is no uptime history to quote you. Two things are missing and named rather than glossed over: the contents of PDF attachments are not read yet (the extractor exists, it is not wired into the pipeline). The n8n node is published in n8n’s verified registry and installs on n8n Cloud and self-hosted n8n. Everything else on this page is live and can be checked with one curl before you spend anything.

Try it against your own email #

The honest test is not a feature table, it is your own worst email. Take the message that your current parser gets wrong, paste its subject and body into POST /v1/parse, and look at the confidence numbers and the evidence spans on the fields it returns. It stores nothing, it needs no address and no DNS record, and the free plan — 300 parsed emails a month, no card — is enough to run a real low-volume workflow rather than only to look at one.

Get an API key   Read the quickstart   API reference

Other comparisons #