◎ Discry Score
klarna.com
payments · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 94 (A)
Discry your API →
PAYMENTS · RANK #23 OF 25

Klarna is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Klarna API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 40/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 63/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Partial
Capability boundariesClear limits — what the API can and cannot do.Partial
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • Klarna has comprehensive multi-step workflow documentation showing the full payment integration flow from initiation through order management
  • An OpenAPI spec exists as a GitHub gist but is not officially hosted on docs.klarna.com, making agent discovery unreliable
  • A Klarna Payments MCP server exists on Glama, auto-generated via AG2 MCP builder
  • Documentation includes dedicated error handling pages with error codes per product (Payments, Order Management)
  • The API reference landing page returns 404, suggesting documentation restructuring may be in progress

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add llms.txt to docs.klarna.com covering core payment flows and API endpoints
  2. 02Host the OpenAPI spec officially at a public URL on docs.klarna.com
  3. 03Add AGENTS.md to the klarna GitHub org with guidance for payment integration agents
  4. 04Fix the API reference introduction page (currently 404)
  5. 05Add .well-known/mcp.json pointing to the Klarna MCP server on Glama

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

API keyOAuth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Klarna uses API key auth and OAuth2. JSON error responses with error codes documented per product. Rate limits documented. Pagination supported.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free