Is callback.com agent ready?
callback.com is not yet agent ready: it scores 22/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (0), Structured Data (1), Content Quality (22), Agent Discovery (30).
Changed since last check
−1 points since the previous check (2026-09-15)
Changed: Response time (partial → fail)
Category scores
Technical
55
Agent Auth
0
Agent Discovery
30
Agent Protocols
0
Content Quality
22
Structured Data
1
Bot Accessibility
66
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ~No error status codespartial
- ✗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 scoredpass
Structured Data
- ✗OpenGraph meta tagsfail
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- —JSON-LD validskip
- ~Heading hierarchypartial
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ~Author attributionpartial
- ~Citation readinesspartial
- ~Lists and tables for structured infopartial
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 resolvefail
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✗Reachable as Google-Agentfail
- ✗Reachable as ChatGPT-Userfail
- ✗Reachable as Perplexity-Userfail
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 charsetfail
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ~Content accessible without JSpartial
- ✓Security headerspass
Score history
- 22/100 · rubric v3.0
- 23/100 · rubric v3.0
- 18/100 · rubric v2.0
- 18/100 · rubric v2.0
- 18/100 · rubric v2.0
- 17/100 · rubric v2.0
- 18/100 · rubric v2.0
- 34/100 · rubric v2.0