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

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

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

Source: https://agentreadycrawlers.com/blog/bloomberg-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

# Bloomberg: the 360 agent-readiness check

In short

Bloomberg scores 49 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. At the door, can't verify agent access. 25 of 82 applicable checks pass; the gap worth most is Developer resource discoverability, about 4.4 points by Ora's estimate. The door could not be measured, so the C is provisional.

Bloomberg is the financial news arm of the terminal business, paywalled for most readers. On 9 November 2026 its public site scored **49 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C, 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: Bloomberg provides structured market data and financial news, but lacks an OpenAPI specification.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 9 of 15 | 60% |
| Access | Can agents read it | 29 of 55 | 53% |
| Usability | Can agents use it | 30 of 72 | 42% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 49 of 100 | 49% |

**

25 checks pass, 10 are partial, 47 fail and 50 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. 2 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/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| robots.txt AI crawler policy | Partial | 1 of 2 | AI search crawlers: allowed in 2 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 0 of 2 checks (2 crawlers on 1 page), not scored. robots.txt restricts 1/3 evaluated search page/crawler pairs. |
| robots.txt agent-user policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://bloomberg.com/. Declared policy only; |
| Content behind auth | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene | Pass | 1 of 1 | Pages agents land on serve real content, not meta-refresh or JavaScript-only redirect stubs that strand non-JS agents |
| 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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Partial | 1 of 3 | Homepage: 8546 chars of readable text, but no H1 tag. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~2K tokens) |
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.bloomberg.com/sitemaps/news/index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) | Pass | 1 of 1 | Dates in your sitemap tell agents what changed and when, so they reread fresh pages instead of guessing. We check lastmod dates parse and the newest is recent. |
| llms.txt exists | Pass | 1 of 1 | Found the llms.txt at https://developer.bloomberg.com/llms.txt. |
| llms.txt formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 46,512 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve | Pass | 2 of 2 | The markdown links an llms.txt declares actually resolve - broken links strand agents that follow the index |
| 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://bloomberg.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data | Partial | 1 of 4 | JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is |
| Organization schema completeness | Fail | 0 of 2 | No Organization type found in JSON-LD |
| JSON-LD entity linking (sameAs) | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Schema type breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| 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 | API described in documentation at https://developer.bloomberg.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://api.bloomberg.com/graphql is reachable; |
| Public API/docs linked from homepage | Pass | 3 of 3 | Documentation site found at https://developer.bloomberg.com |
| Developer portal | Pass | 6 of 6 | Developer documentation portal found at https://developer.bloomberg.com |
| 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 | Fail | 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered |
| 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://bloomberg.com |
| OAuth Protected Resource metadata (RFC 9728) | Pass | 2 of 2 | Metadata at /.well-known/oauth-protected-resource (RFC 9728) that tells agents your auth requirements up front, instead of leaving them to trial and error. |
| 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 document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages | Fail | 0 of 3 | No SDK packages found across language ecosystems |
| 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 | Pass | 4 of 4 | When something breaks, agents need a structured JSON error, not an HTML error page. One is recoverable, the other is a dead end. |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability | Pass | 3 of 3 | bloomberg.com ranks #5 for "Bloomberg" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Bloomberg L.P." and Wikidata Q14270642 both verified - domain confirmed on both sources |
| Developer resource discoverability | Fail | 0 of 3 | In a search for your API docs, none of the 10 results is your official docs |
| NPM/PyPI SDK package | Fail | 0 of 1 | No NPM or PyPI SDK package found |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Listed on skills.sh | Pass | 1 of 1 | Official skills published on skills.sh, the public directory where agents and developers browse for ready-made capabilities. |
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, 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 Bloomberg, 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

Fail, 0 of 3, about 4.4 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs

OpenAPI spec published

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

MCP server / manifest

Fail, 0 of 6, about 3.7 points to gain. Ora saw: No MCP server or manifest found

Scoped permissions

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

WebMCP support

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

## Our read

Bloomberg is the one publisher on this list whose read Ora could not complete at the door: the site blocked a normal browser visit as well as the agents, so bot detection and crawler reachability are recorded as unverifiable rather than failed. Past that, the picture is better than the news average. Five of five sampled pages were readable, the home page returned 8,546 characters without JavaScript, an llms.txt sits at developer.bloomberg.com, and the developer portal there earns the documentation checks. The gaps are the familiar ones: an OpenAPI specification and an MCP server that do not exist, OAuth scopes that are not declared, and a search for the API documentation returned none of Bloomberg's own pages in ten results. A C at 49 with the door unmeasured is a provisional grade; a scan that gets through the bot wall would move it in either direction.

## 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 bloomberg.com, GET /api/score (vendor)](https://ora.ai/api/score/bloomberg.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
-   [Bloomberg home page](https://www.bloomberg.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