--- title: "Citigroup: 44 of 100 on Ora's scan | Am I Ready for Agents?" description: "Citigroup scores 44 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Open to every agent, with 854 characters waiting inside." canonical: https://amireadyforagents.com/blog/citigroup-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Citigroup: 44 of 100 on Ora's scan | Am I Ready for Agents? > Citigroup scores 44 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Open to every agent, with 854 characters waiting inside. Source: https://amireadyforagents.com/blog/citigroup-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Citigroup: 44 of 100 on Ora's agent-readiness scan ## In short Citigroup scores 44 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. The layers read Discovery 10 of 11, Access 19 of 49, Usability 15 of 60. Open to every agent, with 854 characters waiting inside. ## The score Citigroup is a bank based in New York with operations in most of the world's markets. - 44of 100, grade D Ora's agent-readiness scan of citigroup.com, read 9 November 2026. - 10Discovery, of 11 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 19Access, of 49 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 15Usability, of 60 Whether they can act through it: an MCP server, an API with a specification, sign-in for agents. - 0Payments, of 0 No check in this layer applied to the site. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. Ora's one-line summary: Citigroup.com offers developer resource discoverability, but lacks an OpenAPI specification. ## What an assistant meets at the door Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript. | Check | Result | What Ora saw | | --- | --- | --- | | Not blocked by bot detection | Pass, 2 of 2 | Site accessible to 6 AI agent user-agents | | Agent crawler reachability | Pass, 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable | | robots.txt AI crawler policy | Pass, 2 of 2 | Training: 2/2. Search: 3/3 page/crawler pairs permitted. No applicable crawl or usage restriction found for 5 training and search crawlers (gptbot, claudebot, oai-searchbot, claude-searchbot). | | 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://citigroup.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | 854 chars with H1, but 2.4% content ratio is below the 5% target | ## What it can read, and what it can do The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site. | Check | Result | What Ora saw | | --- | --- | --- | | 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). | | Bot-UA markdown serving | Fail, 0 of 1 | No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. | | JSON-LD structured data | Partial, 3 of 4 | JSON-LD Organization found - missing description on this entity | | Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: contactPoint, address | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.citigroup.com/global/sitemap.xml with 3566 entries | | Metadata completeness | Partial, 1 of 2 | 3/4 metadata signals present - missing: og:image | | Page token budget | Pass, 1 of 1 | All 1 measured page fit an agent context budget (largest ~1K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | 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 | | Public API with reachable endpoints | Pass, 7 of 7 | GraphQL endpoint at https://citigroup.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 | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Did not apply, 0 of 6 | No developer portal found | | OAuth 2.0 support | Fail, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected | | Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found | | Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems | | CLI tool available | Did not apply, 0 of 3 | No CLI tool found | | WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 11 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikipedia "Citigroup" verified - create a Wikidata item with P856 (official website) = citigroup.com to complete knowledge graph coverage | | Brand name discoverability | Pass, 3 of 3 | citigroup.com appears at position #2 in a clean brand-name search for "Citi" (1 total match) | | Category share of voice | Did not apply, 0 of 6 | Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name). | | Developer resource discoverability | Pass, 3 of 3 | Agent discovered 1 developer-resource type by name (developer portal) across 2 pages | The six payment checks did not apply on this read: Ora did not read the site as a shop. ## Three fixes to hand to the web team Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it. 1. OpenAPI spec published, worth about 4.8 points by Ora's estimate: No OpenAPI/Swagger specification found. 2. MCP server / manifest, worth about 4.4 points by Ora's estimate: No MCP server or manifest found. 3. OAuth 2.0 support, worth about 3.7 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected. ## Our read Citigroup's door is open and the house is nearly bare. Six AI agent user agents reach citigroup.com, robots.txt permits every training and search pair Ora checked, the sitemap lists 3,566 pages and the Organization block lacks only its description, but the home page gives 854 characters at a 2.4 percent text ratio, the metadata lacks og:image and there is no llms.txt, so the Access layer reads 19 of 49. The Discovery layer is nearly full at 10 of 11: Wikipedia confirms the company and the domain sits second in a clean search for Citi, though no Wikidata item points at it. The act layer is a GraphQL endpoint at citigroup.com/graphql with introspection gated, and nothing around it: no developer portal, no OpenAPI specification, and neither an MCP server nor OAuth discovery, so the Usability layer reads 15 of 60. A bank present in most of the world's markets tells an agent 854 characters; the template is the cheap fix, an OpenAPI specification the one worth most. ## Test your own site Run the same scan on your own domain at [ora.ai](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check). The score, the layers and the fixes on this page come from its public result for citigroup.com; a scan of a public site takes a few minutes and needs no account. - [Scan your domain on Ora](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check)The same checks, the same scoring, on your own site. - [The self-check, 18 questions](https://amireadyforagents.com/self-check)What to ask for, in business terms, before the scan. - [All the 360 checks](https://amireadyforagents.com/blog)The other companies in this series, newest first. ## Sources 1. [Ora report for citigroup.com](https://ora.ai/score/citigroup.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/citigroup.com), read 9 Nov 2026. Vendor claim. Last reviewed 9 November 2026 Reviewed 9 November 2026. [1 source](#sources), each with the day it was read.