Is creditkarma.com agent ready?
creditkarma.com is not yet agent ready: it scores 43/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (20), Agent Protocols (42).
Changed since last check
+2 points since the previous check (2026-09-15)
Fixed: Public API surface
Regressed: Appropriate Schema.org type, Heading hierarchy, Schema.org JSON-LD present, Lists and tables for structured info
Changed: Answer-first content (fail → partial), nextjs-metadata-api (fail → partial)
Category scores
Technical
91
Agent Auth
20
Agent Discovery
0
Agent Protocols
42
Content Quality
51
Structured Data
52
Bot Accessibility
57
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ✗Heading hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ~Lists and tables for structured infopartial
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✓Structured formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- —Agent/bot auth documentationskip
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✗Developer portalfail
- —Scoped API permissionsskip
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ~nextjs-metadata-apipartial
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
Score history
- 43/100 · rubric v3.0
- 41/100 · rubric v3.0
- 41/100 · rubric v3.0
- 37/100 · rubric v2.0
- 37/100 · rubric v2.0
- 39/100 · rubric v2.0
- 39/100 · rubric v2.0