# SNCF — API Agent Score

> Score: 61/100 (Grade: C) | Domain: sncf.fr | Rubric: 1.0.0 | Checked: July 30, 2026

SNCF scored 61/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 84/100 (A)
- Developer Experience: 49/100 (F)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 78/100 (B)
- Agent Usability: 43/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="v2.1" 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 0%.
- [warn] Schema coverage & depth — Only 56% of operations have documented schemas. Investigated: spec 50%, sdk 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Description completeness — 73% description completeness (target 90%+). Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — Newest official SDK activity 28 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Self-service developer portal — No self-service signup detected: no signup link found 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. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 15 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/4 pages return markdown). Investigated: docs 75%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 50%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://numerique.sncf.com/startup/api/llms.txt, https://numerique.sncf.com/llms.txt, https://numerique.sncf.com/docs/llms.txt); 1 failed to fetch. Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 4 distinct 4xx/5xx response codes documented. Investigated: docs 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 — No pages support .md URLs (0/4 tested). Investigated: docs 71%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 2 assessed pages (2 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

SNCF's API design foundation is strong, with a machine-readable contract and clean schema already in place — a solid base for partner integrations. However, the partner program is being held back by two critical gaps: partners have no self-service entry point to discover, understand, and run the APIs without a sales conversation, and agents cannot reliably find, parse, or execute against the API surface. Closing the onboarding and agent-readiness gaps should be the immediate priority to unlock self-serve partner growth and enable AI-powered integrations.