---
title: "Politico agent readiness: the 360 check | Agent Ready Crawlers"
description: "Politico on Ora's agent-readiness scan, read 2026-11-09: 30 of 100, grade D. The door, what agents can read and do, the fixes worth most."
canonical: https://agentreadycrawlers.com/blog/politico-agent-readiness
site: "Agent Ready Crawlers"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Politico agent readiness: the 360 check | Agent Ready Crawlers

> Politico on Ora's agent-readiness scan, read 2026-11-09: 30 of 100, grade D. The door, what agents can read and do, the fixes worth most.

Source: https://agentreadycrawlers.com/blog/politico-agent-readiness
Site: Agent Ready Crawlers
Last reviewed: 2026-11-09
Agent endpoints: https://agentreadycrawlers.com/llms.txt (index), https://agentreadycrawlers.com/openapi.json (API), https://agentreadycrawlers.com/mcp (MCP server), https://agentreadycrawlers.com/ask (search)
Access: https://agentreadycrawlers.com/auth.md (no key). Pricing: https://agentreadycrawlers.com/pricing.md (free).

360 check, 9 November 2026

# Politico: the 360 agent-readiness check

In short

Politico scores 30 of 100 on Ora's agent-readiness scan, a D, read 9 November 2026. At the door, bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. 7 of 72 applicable checks pass; the gap worth most is Developer resource discoverability, about 4.9 points by Ora's estimate. An MCP server and an OAuth endpoint sit behind a challenge page.

Politico is Axel Springer's politics publisher in Washington and Brussels. On 9 November 2026 its public site scored **30 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a D, in Ora's News & Intelligence category. 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. The check below walks through all 132 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: Politico offers a public API with reachable endpoints, but lacks an OpenAPI specification.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 5 of 9 | 56% |
| Access | Can agents read it | 1 of 51 | 2% |
| Usability | Can agents use it | 23 of 60 | 38% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade D | 30 of 100 | 30% |

**

7 checks pass, 15 are partial, 50 fail and 59 do not apply to this site. Every check is defined in [Ora's catalog](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) (read 2026-11-05); the result for each one is in the groups below, with what Ora saw where it said.

## At the door

What the site answers when a request arrives with an agent’s user agent, and what robots.txt says to the crawlers in the Index. 5 checks in this group do not apply to this site and are left out.

Agents named in Ora's results, with their Index rows: [ChatGPT-User](https://agentreadycrawlers.com/crawlers/chatgpt-user/), [OAI-SearchBot](https://agentreadycrawlers.com/crawlers/oai-searchbot/), [Claude-User](https://agentreadycrawlers.com/crawlers/claude-user/), [PerplexityBot](https://agentreadycrawlers.com/crawlers/perplexitybot/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass, |
| Agent crawler reachability | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 4 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Partial | 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Sitemap exists | Fail | 0 of 2 | No sitemap found |
| llms.txt exists | Fail | 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://politico.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Agent mode view | Fail | 0 of 2 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data | Partial | 0 of 4 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check Organization schema |
| JSON-LD entity linking (sameAs) | Partial | 0 of 2 | Homepage blocked by WAF - cannot check entity linking |
| Schema type breadth | Partial | 0 of 2 | Homepage blocked by WAF - cannot check schema types |
| Metadata completeness | Partial | 0 of 2 | Homepage blocked by WAF - cannot check metadata |
| Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, a command line.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Public API with reachable endpoints | Pass | 7 of 7 | GraphQL endpoint at https://api.politico.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage | Partial | 0 of 3 | Homepage blocked by WAF - cannot check for docs links |
| Developer portal | Fail | 0 of 6 | No developer portal found |
| OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| MCP server / manifest | Partial | 5 of 6 | MCP server detected at https://mcp.politico.com; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery | Partial | 1 of 2 | MCP server at https://mcp.politico.com - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://auth.politico.com |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) |
| CLI tool available | Pass | 3 of 3 | CLI package found on npm: @politico/interactive-bin |
| Multi-language SDK packages | Partial | 1 of 3 | SDK package found only in npm |
| Rate limit response headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability | Pass | 3 of 3 | politico.com ranks #3 for "politico" (searched your brand name alone: we could not read a product term from your site) |
| Wikipedia / Wikidata entity presence | Unverified | 0 of 4 | Wikipedia and Wikidata presence could not be verified - try rescanning |
| Developer resource discoverability | Partial | 1 of 3 | Name search surfaced no pages on politico.com, although developer resources exist on the site (MCP server) - weak search indexing or transient search noise |
| Listed in MCP registries | Fail | 0 of 1 | No bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, |
| NPM/PyPI SDK package | Pass | 1 of 1 | An official SDK or CLI on NPM or PyPI gives agents and the developers steering them a ready-made way in, instead of hand-rolling every API call. |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json (and no legacy /.well-known/ai-catalog.json) |

## 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 Politico, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog.

Developer resource discoverability

Partial, 1 of 3, about 4.9 points to gain. Ora saw: Name search surfaced no pages on politico.com, although developer resources exist on the site (MCP server) - weak search indexing or transient search noise

OpenAPI spec published

Fail, 0 of 7, about 4.6 points to gain. Ora saw: No OpenAPI/Swagger specification found

Developer portal

Fail, 0 of 6, about 3.9 points to gain. Ora saw: No developer portal found

Scoped permissions

Fail, 0 of 5, about 3.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found

WebMCP support

Fail, 0 of 5, about 3.7 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found

## Our read

Politico has more agent infrastructure than its score suggests. Ora detected an MCP server at mcp.politico.com, an OpenID Connect endpoint at auth.politico.com, a reachable GraphQL API, an npm package and a CLI, which is why the Usability layer reads 23 of 60 while the Access layer reads 1 of 51. The door is the problem: a bot-management challenge met all four test agents and answered 403 to the robots.txt request as well, so Ora could not say what the policy permits. There is no sitemap, no llms.txt and no developer portal to tie the pieces together, and the Wikipedia and Wikidata checks could not be verified on this read. For an Axel Springer title with a working MCP server behind the wall, a D at 30 is mostly a WAF rule and a missing portal page.

## Check your own door

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then compare the door with the [Block Rate Report](https://agentreadycrawlers.com/block-rates/) for sites of your rank and kind. Our [guide to testing whether agents can reach your site](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) has the curl commands for a manual check, and the [robots.txt builder](https://agentreadycrawlers.com/robots-builder/) writes a policy file from the Index. Payments did not apply to this site; a site that sells would read that layer against the [vendors at the door](https://agentreadycrawlers.com/vendors/ranking/).

[Scan your own domain on Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)

[All 360 checks](https://agentreadycrawlers.com/blog/). One company a day; corrections to [the corrections page](https://agentreadycrawlers.com/corrections/).

**

The check we recommend

[Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) scans a public URL: 16 Discovery checks and 42 Access checks, read from its catalog on 2026-11-05. Its Journey sends a real agent to the site. [How to run it](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/).

**Limits.** Ora reads public URLs only, and what it records as blocked comes from its own network. It says the same scan run twice converges within a couple of points ([Ora's Deep Scan post](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)), and the pages we read give no repeat-scan figures. Its fixing product is behind a waitlist ([Ora's home page](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)).

## Sources

-   [Ora's scan of politico.com, GET /api/score (vendor)](https://ora.ai/api/score/politico.com?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-09
-   [Ora's check catalog, GET /api/checks (vendor)](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Politico home page](https://www.politico.com/) read 2026-11-09
-   [How to test whether AI agents can reach your site (this site)](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) read 2026-11-04
-   [Ora: Deep Scan v2 (vendor)](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05
-   [Ora home page, waitlist (vendor)](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05

Last reviewed 2026-11-09