# Mollie — API Agent Score

> Score: 81/100 (Grade: A) | Domain: mollie.com | Rubric: 1.0.0 | Checked: July 24, 2026

Mollie scored 81/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/mollie)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 81/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 75/100 (B)
- Agent Discovery: 75/100 (B)
- Agent Understanding: 85/100 (A)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Schema coverage & depth — 58/58 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — 99% example coverage across params + responses. Investigated: spec 100%, sdk 100%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://my.mollie.com/dashboard/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 96% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 80%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/mollie, 2188 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt is 107,043 characters (exceeds 100,000 threshold; will be truncated by most agents). Investigated: docs 71%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 50 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 8 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 50 of 51 endpoints have aggressive caching or missing cache headers. Investigated: docs 80%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — 100% of mutating operations document idempotency. Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Pagination documented & consistent — 8/8 list method(s) return an auto-paginating iterable. Investigated: sdk 100%.
- [pass] Sandbox separation — Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Mollie's API program is in strong shape on contract quality and documentation structure, but two gaps put partner and agent adoption at risk. First, there is no machine-readable context file to orient AI agents, meaning agents integrating with Mollie's APIs must guess at conventions, authentication patterns, and workflow guidance rather than reading authoritative instructions. Second, there are no runnable, test-backed collections, so partners and their coding agents lack a verified, executable starting point — slowing the path to a first working integration. Closing these two gaps, plus adding a lightweight quickstart and rate-limit response headers, will materially shorten the time partners spend going from discovery to live traffic.