# Mercadona — API Agent Score

> Score: 57/100 (Grade: D) | Domain: mercadona.es | Rubric: 1.0.0 | Checked: September 3, 2026

Mercadona scored 57/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 57/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 92/100 (A+)
- Agent Understanding: 40/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt is present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://www.mercadona.es/, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — A full-corpus llms-full.txt is published at https://mercadona.es/llms-full.txt, so agents can ingest all your docs in one fetch. Investigated: docs 100%.
- [pass] Registry & SDK presence — Official SDKs found in 5 distinct languages, covering the ones agents use most. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 0 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 50%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [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

- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Mercadona's API program shows strong discoverability fundamentals, but two critical gaps are blocking partner and agent productivity. Coding agents have no structured setup or usage instructions to work from, and there is no executable, runnable representation of the API that partners or agents can use to make a verified first call. Closing these two gaps — agent context files and a public runnable workspace — should be the immediate priority to unlock self-serve partner onboarding and reliable AI-assisted integration.