lemon.markets is Needs Work to agents.
Discry independently scored how well an AI agent can discover and understand the lemon.markets API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
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 · 50/100Comprehension
55% of score · 91/100What we found
- An agent lands on documentation that is explicitly built for it: every page opens with 'For AI agents: visit llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI.' The llms.txt is a clean, ~14KB API-focused index covering guides, ~90 endpoint references, and changelogs — comprehension scores an A (91).
- Endpoint docs are genuinely task-oriented ('Buy shares of an instrument and pay with cash', 'Place Orders on Behalf of Users') and examples use realistic values (real ISINs like US0378331005, UUID idempotency keys, EUR amounts) across Shell/Python/Go — copy-pasteable for an agent.
- The idempotency guide is a standout: it documents retry-safety, key expiry, and a full error-scenario table — exactly the self-correction guidance agents need to recover from timeouts without duplicating orders.
- Discovery is the weak dimension (D, 50): no AGENTS.md in any lemon-markets repo, no MCP server listed in Glama/Smithery/PulseMCP, and no publicly downloadable OpenAPI spec file — the legacy paper-trading spec host is dead and the reference is OpenAPI-backed but not fetchable.
- The sitemap is broken: developer.lemon.markets has none, and the marketing sitemap.xml is misconfigured with localhost:3000 URLs and lists zero documentation pages — an agent crawling for structure would find nothing and no doc URLs are discoverable that way.
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Expose a publicly downloadable OpenAPI/Swagger spec at a stable URL (e.g. developer.lemon.markets/openapi.json). The reference is already OpenAPI-generated in ReadMe — surfacing the raw spec is the single highest-impact discovery fix and would let agents/SDKs consume the full contract in one fetch.
- 02Fix the sitemap: the marketing sitemap.xml currently emits localhost:3000 URLs and no doc pages. Publish a valid sitemap that includes developer.lemon.markets documentation and reference pages so crawlers and agents can enumerate the surface.
- 03Add an AGENTS.md to the primary lemon-markets GitHub repos (and/or an SDK repo) with setup, auth, and safe-usage context for coding agents — a rising standard that currently returns nothing.
- 04Ship an llms-full.txt (ReadMe can generate one) so an agent can pull comprehensive markdown in a single request instead of walking ~90 individual .md endpoint pages.
- 05Publish rate-limit and pagination documentation (limits, headers, cursor/offset behaviour). Both are currently absent and are exactly the boundaries an agent would otherwise discover only by failing.
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.
Auth is a Bearer API key plus two mandatory data-privacy tracing headers (LMG-Data-Privacy-Access-Principal / -Justification), all clearly documented. Errors return machine-parseable JSON with a `message` field and standard HTTP codes (400/401/404/422/5XX) listed per endpoint. Idempotency is documented to a Stripe-grade standard (IETF draft key header, 24h expiry, replay/error scenarios). Rate limits and pagination behaviour are not documented in the public hub.