# Europa — API Agent Score

> Score: 65/100 (Grade: C) | Domain: europa.eu | Rubric: 1.0.0 | Checked: October 23, 2026

Europa scored 65/100 (C), classified "partially-ready".

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

## Summary

- Overall: 65/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 76/100 (B)
- Developer Experience: 45/100 (F)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 89/100 (A)
- Agent Usability: 47/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 2 of 76 public signatures use loose types (anyTypeRatio=0.026). Investigated: sdk 93%, spec 75%.
- [warn] Machine-readable, versioned contract — The API sets a version ("5.3.13") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 88%, docs 75%, cli 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [warn] Auth declared & discoverable — The spec declares no authentication scheme, so an agent can't tell how to authenticate a request. Investigated: spec 25%, docs 25%, cli 0%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, cli 0%.

### Developer Experience

- [pass] Description completeness — 94% of operations and parameters carry substantive descriptions (51 of 55 ops, 155 of 163 params), the main semantic cue an agent relies on. Investigated: spec 100%, sdk 100%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (ec-europa/europa-component-library, 2259 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 12 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.ted.europa.eu/api/latest/index.html/llms.txt, https://docs.ted.europa.eu/llms.txt, https://docs.ted.europa.eu/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 3 distinct 4xx/5xx error codes are documented (plus 0 catch-all "default" responses), so an agent has limited failure branching. Investigated: docs 100%, spec 50%, cli 0%.
- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (camelCase). Investigated: sdk 100%, spec 75%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, cli 0%, wellknown 0%.
- [fail] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 0% (threshold 35% for full credit).
- [skip] Docs structured data — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 28) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%, sdk 0%, cli 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — The 3 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: spec 0%, docs 0%.

## Executive Summary

Europa's API program has a solid foundation in API design and agent understanding, but partners and their agents face significant friction at every stage of onboarding and runtime operation. The two most urgent gaps are a complete absence of self-service onboarding infrastructure — no portal, no quickstart, no changelog — and missing operational reliability signals (idempotency, rate-limit headers, pagination) that will cause AI agents to produce duplicate writes, get throttled silently, and read unbounded datasets. Fixing self-service access and operational reliability in parallel will unlock partner adoption and make the API safe for automated, agent-driven integrations.