Is blink.new agent ready?
blink.new is largely agent ready: it scores 63/100 (grade B) on the w2agent rubric. Weakest areas: Agent Discovery (38), Agent Protocols (44).
Changed since last check
−6 points since the previous check (2026-09-16)
Fixed: Appropriate Schema.org type, Heading hierarchy
Regressed: PKCE S256 support, Discoverable API endpoints, Agent/bot auth documentation, Author attribution
Changed: Response time (fail → partial), Freshness signals (fail → partial)
Category scores
Technical
89
Agent Auth
53
Agent Discovery
38
Agent Protocols
44
Content Quality
61
Structured Data
78
Bot Accessibility
84
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- ✓Declared AI usage preferencestracked, not scoredpass
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ~JSON-LD validpartial
- ✓Heading hierarchypass
- ✓Schema.org JSON-LD presentpass
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ~Freshness signalspartial
- ~Author attributionpartial
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- ✓MCP server cardtracked, not scoredpass
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✗Structured formsfail
- —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 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ~Agent/bot auth documentationpartial
- ✓OAuth discovery chain (RFC 9728 → RFC 8414)pass
- —Developer portalskip
- —Scoped API permissionsskip
- ✓API catalog (RFC 9727)pass
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✓nextjs-metadata-apipass
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 63/100 · rubric v3.0
- 69/100 · rubric v3.0
- 63/100 · rubric v3.0
- 64/100 · rubric v2.0
- 64/100 · rubric v2.0
- 63/100 · rubric v2.0
- 64/100 · rubric v2.0
- 56/100 · rubric v2.0
- 56/100 · rubric v2.0
- 56/100 · rubric v2.0