lovable.dev agentic web readiness

B Manifest validity: 100% (2/2 valid, 0 errors, 3 warnings) · Surface score 41 (coverage 20 + breadth 6 + conformance 15). 4 standards observed across 2 of 9 steps; 2 manifests present (+ security.txt), 0 errors, 3 warnings. Checked 2026-10-25 03:15:00 UTC. This grades the agent-facing files published at lovable.dev, not the organisation's products.

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

Coverage by step

Manifests

What an agent can call

• llms.txt: Lovable, 44 links
• robots.txt AI policy: unlisted crawlers partial

Standards observed

• llms.txt https://lovable.dev/llms.txt
• AI Crawler User-Agent Tokens in robots.txt https://lovable.dev/robots.txt
• Identity Assertion JWT Authorization Grant https://lovable.dev/.well-known/oauth-authorization-server
• OAuth Client ID Metadata Document https://lovable.dev/.well-known/oauth-authorization-server

Cheapest next steps

1. 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": "lovable.dev"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for lovable.dev

   # Lovable for agents
   
   Lovable and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://lovable.dev/llms.txt
   - API description: https://lovable.dev/openapi.json
   - Discovery catalog: https://lovable.dev/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://lovable.dev/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@lovable.dev
   

3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "lovable.dev"}))

Agent pre-flight & practical readiness

Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read. Split-brain llms.txt: lovable.dev/llms.txt has 44 links while docs.lovable.dev/llms.txt has 271 technical links. Probe docs.lovable.dev for full developer documentation.

Fetch: GET https://lovable.dev/llms.txt GET /llms.txt and follow its links.

Subdomain discovery hint (split_brain_llms_txt): Split-brain llms.txt: lovable.dev/llms.txt has 44 links while docs.lovable.dev/llms.txt has 271 technical links. Probe docs.lovable.dev for full developer documentation. (check docs.lovable.dev)

Practical readability: exa_parsable no, markdown negotiation no, render blocked, HTML quality blocked.

AI crawler posture: waf_challenged · Assistant access: OpenAI blocked, Anthropic blocked, Google blocked, Perplexity blocked, Exa blocked.

Readiness subscores: reach 15/20, readability 0/30, capabilities 4/35, conformance 15/15, total 34/100, grade C.

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