v0.app agentic web readiness

B Manifest validity: 0 manifests published (0 errors, 3 warnings) · Surface score 33 (coverage 30 + breadth 3 + conformance 0). 3 standards observed across 3 of 9 steps; 0 manifests present, 0 errors, 3 warnings. Checked 2026-10-25 19:23:08 UTC. This grades the agent-facing files published at v0.app, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/v0.app.svg) · JSON · Markdown · Re-check now

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 ReadMarkdown for Agents 05 Act 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 404
MCP Server Cards (SEP-2127) `/mcp/server-card`	soft-404 HTML	answered with an HTML page (catch-all or soft 404), counted as absent
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	soft-404 HTML	answered with an HTML page (catch-all or soft 404), counted as absent
AGENTS.md `/AGENTS.md`	soft-404 HTML	answered with an HTML page (catch-all or soft 404), counted as absent
Agent Skills `/.well-known/agent-skills/index.json`	absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	no AI tokens	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (allowed) no Agentmap: line (optional convention pointing agents at /.well-known/ard.json) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	soft-404 HTML	answered with an HTML page (catch-all or soft 404), counted as absent
Open Knowledge Format `/okf/index.md`	soft-404 HTML	answered with an HTML page (catch-all or soft 404), counted as absent

What an agent can call

MCP endpoint https://v0.app/api/mcp (streamable-http) — from /.well-known/oauth-protected-resource
robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed
OAuth protected resource https://v0.app/api/mcp, authorization servers: https://v0.app

Standards observed

OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://v0.app/.well-known/oauth-protected-resource
Markdown for Agents https://v0.app/
Model Context Protocol

Cheapest next steps

llms.txt: one Markdown index file; the most widely read agent-facing file

Generate starter /llms.txt for v0.app

# V0

> V0 and what it offers to agents

Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.

## Docs
- [Getting started](https://v0.app/docs/getting-started): the first page to read
- [API reference](https://v0.app/openapi.json): OpenAPI description

## Optional
- [Changelog](https://v0.app/changelog): what changed, newest first

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "v0.app"}))

AGENTS.md: instructions for coding agents working on or with the site

Generate starter /AGENTS.md for v0.app

# V0 for agents

V0 and what it offers to agents

## Read the data, not the HTML
- Index: https://v0.app/llms.txt
- API description: https://v0.app/openapi.json
- Discovery catalog: https://v0.app/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://v0.app/mcp
- Rate limits and authentication: describe them here

## Conventions
- How to cite or attribute content
- What not to do (no scraping of /account/, no automated sign-ups, etc.)

Contact: security@v0.app

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback markdown_negotiation). Call the MCP endpoint at https://v0.app/api/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://v0.app/api/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 30/30, capabilities 16/35, conformance 0/15, total 66/100, grade A.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules