Is chargeblast.com agent ready?
chargeblast.com is not yet agent ready: it scores 43/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (27), Content Quality (37), Structured Data (40).
Changed since last check
−10 points since the previous check (2026-09-15)
Regressed: Appropriate Schema.org type, Freshness signals
Changed: JSON-LD valid (partial → fail), Schema.org completeness (partial → fail)
Category scores
Technical
96
Agent Auth
0
Agent Discovery
50
Agent Protocols
27
Content Quality
37
Structured Data
40
Bot Accessibility
82
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓XML sitemap existspass
- ✓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 tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ✗Heading hierarchyfail
- ✓Schema.org JSON-LD presentpass
- ✗Schema.org completenessfail
Content Quality
- ✗FAQ contentfail
- ✓Answer-first contentpass
- ~Content lengthpartial
- ~Token efficiency (HTML-to-text ratio)partial
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✗Lists and tables for structured infofail
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- ✗/.well-known/ucpfail
- —Structured formsskip
- —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 surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- —ecommerce-gtin-validskip
- —ecommerce-product-schemaskip
- ✓ecommerce-checkout-accessiblepass
Score history
- 43/100 · rubric v3.0
- 53/100 · rubric v3.0
- 54/100 · rubric v3.0
- 35/100 · rubric v2.0
- 35/100 · rubric v2.0
- 34/100 · rubric v2.0
- 35/100 · rubric v2.0
- 35/100 · rubric v2.0