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

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

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

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

# Investopedia: the 360 agent-readiness check

In short

Investopedia scores 28 of 100 on Ora's agent-readiness scan, a D, read 9 November 2026. At the door, could not test bot user agents. 7 of 71 applicable checks pass; the gap worth most is Brand name discoverability, about 4.4 points by Ora's estimate. Agent infrastructure built and then hidden behind the door.

Investopedia is Dotdash Meredith's finance reference site, whose parent licensed content to OpenAI. On 9 November 2026 its public site scored **28 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: Investopedia offers public API endpoints with OAuth 2.0 support, but lacks an OpenAPI specification for agent discovery.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 6 of 15 | 40% |
| Access | Can agents read it | 4 of 53 | 8% |
| Usability | Can agents use it | 25 of 67 | 37% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade D | 28 of 100 | 28% |

**

7 checks pass, 8 are partial, 56 fail and 54 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. 3 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/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Unverified | 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Fail | 0 of 2 | No agent we tested can reach the homepage - ChatGPT-User: blocked, OAI-SearchBot: blocked, Claude-User: blocked, PerplexityBot: blocked |
| robots.txt AI crawler policy | Partial | 1 of 2 | AI search crawlers: allowed in 1 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 1 of 2 checks (2 crawlers on 1 page), not scored. robots.txt restricts 2/3 evaluated search page/crawler pairs. |
| robots.txt agent-user policy | Partial | 1 of 2 | robots.txt restricts 2/3 evaluated page/crawler pairs. Checked 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page. Restricted: claude-user at https://investopedia.com/ (Disallow: /, |
| 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. 3 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Unverified | 0 of 3 | Could not fetch homepage |
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.investopedia.com/sitemap.xml with multiple sitemaps entries |
| 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://investopedia.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 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data | Unverified | 0 of 4 | Could not fetch homepage |
| Organization schema completeness | Unverified | 0 of 2 | Company details (contact, address) in your structured data. AIs use them to verify you are a real business before recommending you. |
| JSON-LD entity linking (sameAs) | Unverified | 0 of 2 | sameAs links from your structured data to your official profiles (GitHub, LinkedIn, app stores). They let AIs confirm that every mention of you is actually you. |
| Schema type breadth | Unverified | 0 of 2 | The more kinds of content you mark up with schema.org (FAQs, reviews, services, events, videos), the more kinds of questions an AI can answer about you with confidence. |
| Metadata completeness | Unverified | 0 of 2 | Could not fetch homepage |
| 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.investopedia.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 | Fail | 0 of 3 | No public API or documentation page linked from homepage |
| 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://support.investopedia.com/mcp; 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://support.investopedia.com/mcp - 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 | OAuth authorization server metadata at https://support.investopedia.com/mcp/oauth |
| 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 | 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 | Fail | 0 of 3 | investopedia.com was not in the top 10 for "investopedia" (searched your brand name alone: we could not read a product term from your site) |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Investopedia" and Wikidata Q6060906 both verified - domain confirmed on both sources |
| Developer resource discoverability | Partial | 1 of 3 | Name search surfaced no pages on investopedia.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 | Fail | 0 of 1 | No NPM or PyPI SDK package found |
| 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 |
| 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 |

## Payments

The agent payment protocols Ora probes for. Most sites outside commerce have nothing here, and Ora scores the layer out of zero when none applies. 5 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| x402 payment protocol | Partial | 0 of 2 | HTTP 402 at GET https://investopedia.com/api without a PAYMENT-REQUIRED header |

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

Brand name discoverability

Fail, 0 of 3, about 4.4 points to gain. Ora saw: investopedia.com was not in the top 10 for "investopedia" (searched your brand name alone: we could not read a product term from your site)

OpenAPI spec published

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

Developer portal

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

Scoped permissions

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

WebMCP support

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

## Our read

Investopedia's read is a study in a site that built agent infrastructure and then hid it. Ora detected an MCP server behind authentication at support.investopedia.com/mcp with OAuth metadata beside it and a reachable GraphQL endpoint at api.investopedia.com, which lift the Usability layer to 25 of 67. At the front, though, no test agent reached the home page, the bot user agents could not be tested, robots.txt restricts two of three user-triggered agents and allows one search crawler of three, and the page could not be fetched. The Discovery layer at 6 of 15 carries the odd result: investopedia.com did not appear in the top ten for a search on its own name, though Wikipedia and Wikidata confirm the domain. Dotdash Meredith licensed this content to OpenAI; a D at 28 is the public face of a deal done at the API.

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