# Atos — API Agent Score

> Score: 51/100 (Grade: D) | Domain: atos.com | Rubric: 1.0.0 | Checked: July 30, 2026

Atos scored 51/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 64/100 (C)
- Agent Discovery: 62/100 (C)
- Agent Understanding: 67/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [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 at https://www.atos.com/register; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [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] Registry & SDK presence — Discovered SDKs in 5 distinct languages. Investigated: sdk 100%, wellknown 50%, docs 0%, cli 0%, mcp 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 60%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://atos.net/en/llms.txt, https://atos.net/llms.txt, https://atos.net/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 86%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. 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] 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 discovered for the org. 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

Atos's API program shows meaningful strength in crawlability and doc parseability, but faces critical gaps that will slow or block partner adoption: the two most urgent are an absence of runnable, agent-ready context (making it impossible for partners and their AI agents to safely validate integrations) and missing machine-readable discovery surfaces (meaning partners and agents cannot find or consume your APIs without a manual introduction). Closing these gaps — alongside tightening auth/security hygiene and adding a quickstart — will shift the program from a gated, high-friction experience to a self-serve partner channel that both humans and AI agents can onboard against independently.