--- title: "Deutsche Telekom: the 360 check | Agent Ready Checklist" description: "Deutsche Telekom on Ora's agent-readiness scan, read 2026-11-09: 50 of 100, grade C. 5 of 21 checklist rows met, 12 not met." canonical: https://agentreadychecklist.com/blog/deutsche-telekom-agent-readiness site: "Agent Ready Checklist" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Deutsche Telekom: the 360 check | Agent Ready Checklist > Deutsche Telekom on Ora's agent-readiness scan, read 2026-11-09: 50 of 100, grade C. 5 of 21 checklist rows met, 12 not met. Source: https://agentreadychecklist.com/blog/deutsche-telekom-agent-readiness Site: Agent Ready Checklist Last reviewed: 2026-11-09 Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search) Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free). # Deutsche Telekom against the checklist: the 360 agent-readiness check 360 check, 9 November 2026. Deutsche Telekom is Europe's largest telecoms group and the owner of T-Mobile US. Deutsche Telekom scores 50 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. At the door, site accessible to 6 AI agent user-agents. 5 of the 21 checklist rows with an Ora check are met. 1 of 3 MUST rows is met. Real developer surfaces described to humans only, under a page titled Corporate Website. On 9 November 2026 the public site at telekom.com scored **50 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. Below, each of the 31 checklist rows is read against the Ora checks the [crosswalk](https://agentreadychecklist.com/checklist/ora-checks/) names for it, so the result says which requirements this company meets, not only how many points it scored. Ora's one-line summary: Telekom has SDK packages and training corpus coverage, but lacks OpenAPI specs and developer resource discoverability. ## The score | Layer | Points | Share | What the layer asks | | --- | --- | --- | --- | | Discovery | 16 of 32 | 50% | Can agents find and recommend it | | Identity | 32 of 62 | 52% | Can agents tell what it is | | Access | 32 of 50 | 64% | Can agents read it | | Agent Integration | 23 of 60 | 38% | Can agents integrate with it | | User Experience | 5 of 9 | 56% | How the site reads inside an agent | | Total | 50 of 100 | 50% | Grade C | ## Row by row A row is met when every Ora check the crosswalk names for it passes, not met when every one fails, and partly when the checks disagree or one is partial. A row with no Ora check in the catalogue, or whose checks did not apply to this site, is marked as such; the [Verify Kit](https://agentreadychecklist.com/kit/) tests those by hand. | Row | Level | Result | Ora checks, and what Ora saw | | --- | --- | --- | --- | | AR-FIND-01; Do not block agents | MUST | Partly | robots.txt AI crawler policy (fail), robots.txt agent-user policy, Agent crawler reachability, Not blocked by bot detection (pass).; No AI crawler directives in robots.txt | | AR-FIND-02; Answers on one first-party page | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-FIND-03; Sitemap listed in robots.txt | SHOULD | Met | Sitemap exists (pass).; Valid sitemap found at https://www.telekom.com/service-sitemap-46d71a0aa936124d85407c84e988d231-sitemap_index.xml with multiple sitemaps entries | | AR-FIND-04; AI Catalog at .well-known | MAY | No Ora check | AI Catalog discovery, ARD discovery. | | AR-READ-01; Answer in the initial HTML | MUST | Met | Content without JavaScript (pass).; 4275 chars with H1 but flat heading structure | | AR-READ-02; Real HTTP status codes | MUST | No Ora check | Redirect hygiene. | | AR-READ-03; Home page with real links | SHOULD | Met | Public API/docs linked from homepage (pass).; Documentation site found at https://developer.telekom.com | | AR-READ-04; Docs that answer agent tasks | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-READ-05; Fenced, language-tagged code | SHOULD | No Ora check | Code fence validity. | | AR-READ-06; Link the discovery files | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-READ-07; Ship llms.txt | SHOULD | Partly | llms.txt exists (partial), llms.txt formatting (fail), llms.txt links resolve.; A file is present at https://developer.telekom.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt. | | AR-READ-08; JSON-LD on key pages | SHOULD | Not met | JSON-LD structured data (fail).; No JSON-LD structured data found on homepage | | AR-READ-09; Advertise a markdown mirror | MAY | No Ora check | Markdown alternate link. | | AR-READ-11; Pricing as first-party HTML | SHOULD | Met | Pricing info accessible (pass).; Pricing info accessible: pass, 3 of 3. | | AR-ACT-01; Auth an agent can finish | SHOULD | Partly | OAuth 2.0 support (partial), Scoped permissions (pass).; OAuth mentioned in documentation at https://developer.telekom.com | | AR-ACT-02; OpenAPI contract | SHOULD | Not met | OpenAPI spec published (fail).; No OpenAPI/Swagger specification found | | AR-ACT-03; MCP over Streamable HTTP | SHOULD | Not met | MCP server / manifest (fail), Listed in MCP registries (not applicable), MCP PKCE S256 support (not applicable), MCP OAuth metadata (not applicable).; No MCP server or manifest found | | AR-ACT-04; MCP server card | MAY | Not met | MCP server-card.json (fail).; No MCP server card found at /.well-known/mcp/server-card.json | | AR-ACT-05; MCP Apps view | MAY | Not met | MCP Apps support (fail).; No MCP Apps support detected (optional bonus - only counted if implemented) | | AR-ACT-06; SDKs and a CLI | SHOULD | Partly | CLI tool available (fail), Multi-language SDK packages (partial), NPM/PyPI SDK package (pass).; No CLI tool found | | AR-ACT-07; WebMCP tools | SHOULD | Not met | WebMCP support (fail).; No WebMCP support detected | | AR-ACT-08; Agent payments | MAY | Met | x402 payment protocol (not applicable), MPP payment protocol (not applicable), UCP - Universal Commerce Protocol (not applicable), ACP - Agentic Commerce Protocol (not applicable), ACP delegate payment (pass).; ACP delegate payment: pass, 3 of 3. | | AR-ACT-09; NLWeb /ask endpoint | MAY | Not met | NLWeb /ask endpoint (fail).; No NLWeb /ask endpoint found | | AR-ACT-10; An MCP server or a CLI | MUST | Not met | MCP server / manifest (fail), CLI tool available (fail).; No MCP server or manifest found | | CF-CONTENT-SIGNALS; Content-Signal line | cloudflare | No Ora check | No check in Ora's catalogue names this row. | | CF-MARKDOWN-NEGOTIATION; Markdown by Accept | cloudflare | Not met | Markdown content negotiation (acceptmarkdown.com) (fail), Markdown agent docs (fail).; Not acceptmarkdown.com compliant: Accept: text/markdown returned text/html;charset=utf-8; Vary header missing Accept (got "origin, access-control-request-method, access-control-request-headers, accept-encoding") | | CF-PAY-PER-CRAWL; Pay per crawl, HTTP 402 | cloudflare | No Ora check | No check in Ora's catalogue names this row. | | CF-OAUTH-DISCOVERY; OAuth discovery files | cloudflare | Not met | OAuth Protected Resource metadata (RFC 9728) (fail).; No /.well-known/oauth-protected-resource found (RFC 9728) | | CF-AGENT-SKILLS; Agent Skills index | cloudflare | No Ora check | Agent Skills index conformance (v0.2.0) (not applicable). | | VERCEL-NEGOTIATION-HEADERS; Markdown headers | vercel | Not met | Markdown content negotiation (acceptmarkdown.com) (fail).; Not acceptmarkdown.com compliant: Accept: text/markdown returned text/html;charset=utf-8; Vary header missing Accept (got "origin, access-control-request-method, access-control-request-headers, accept-encoding") | | VERCEL-ROBOTS-EXCLUSIONS; Robots exclusions | vercel | Not met | robots.txt AI crawler policy (fail), robots.txt agent-user policy.; No AI crawler directives in robots.txt | ## The fixes worth most points Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Deutsche Telekom, each tied to the checklist row whose recipes cover it. OpenAPI spec published Fail, 0 of 7, about 4.5 points to gain. Ora saw: No OpenAPI/Swagger specification found. Row [AR-ACT-02](https://agentreadychecklist.com/checklist/ar-act-02/), OpenAPI contract. Developer resource discoverability Fail, 0 of 6, about 3.5 points to gain. Ora saw: Agent searched for "telekom" developer resources but found nothing relevant. No checklist row names this check. MCP server / manifest Fail, 0 of 6, about 1.9 points to gain. Ora saw: No MCP server or manifest found. Row [AR-ACT-03](https://agentreadychecklist.com/checklist/ar-act-03/), MCP over Streamable HTTP. Brand name discoverability Fail, 0 of 3, about 1.8 points to gain. Ora saw: "Corporate Website" search returned 9 results but domain did not appear - brand may be too generic or not indexed. No checklist row names this check. API schema complexity analysis Fail, 0 of 2, about 1.3 points to gain. Ora saw: No API schema detected. No checklist row names this check. ## Our read Deutsche Telekom has the surfaces and loses the points on how they are described. developer.telekom.com documents a REST API through its API portal and scores 7 of 7 on Ora's API check, OAuth is described in the documentation, and the door is open to all six AI agent user agents Ora sent. What is missing is the machine-readable layer on top: no OpenAPI specification, an llms.txt at developer.telekom.com/.well-known/llms.txt that returns HTML, and no JSON-LD on a home page whose title is Corporate Website, which is why Ora's brand search for the domain came back empty. The home page itself is generous, 4,275 characters with an H1 and a flat heading structure. Ora read telekom.com with a five-layer model, Agent Integration at 23 of 60 among them. One specification file and one real title would move Europe's largest telecoms group out of the C band. ## Verify your own site The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then take each failing row to its recipe on this site. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy. Payments did not apply to this company; a site that sells is read on that layer too. [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/). ```bash npx ax@0.10 audit https://example.com --min-score 70 ``` [All 360 checks](https://agentreadychecklist.com/blog/), one company a day. Corrections to [the corrections page](https://agentreadychecklist.com/corrections/). ## Sources - [ora.ai/api/score/telekom.com, Ora's scan (vendor)](https://ora.ai/api/score/telekom.com?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check)read 2026-11-09 - [ora.ai/api/checks, contract 1.38.0 (vendor)](https://ora.ai/api/checks?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check)read 2026-11-05 - [telekom.com, the company's site](https://www.telekom.com/)read 2026-11-09 Edition Data 2026-11-04 Reviewed 2026-11-05 Spec AgentReady v2.0, 273d2d7 Crawl 13,071 rows, 2026-11-04 Ora 132 checks, contract 1.38.0, 2026-11-05 Verify with Ora The scanner this site recommends for the whole checklist. 132 checks, a score out of 100, no account. `npx ax@0.10 audit --min-score ` [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/) Method - [How rows, commands and rates are made](https://agentreadychecklist.com/method/) - [How an Ora check is matched to a row](https://agentreadychecklist.com/checklist/ora-checks/) - [Pass rates by rank band](https://agentreadychecklist.com/data/by-rank/) Sources and read dates sit at the foot of the page. Last reviewed 2026-11-09. AgentReady v2.0, read 2026-11-04.