Agent readiness

Agent readiness is the set of conventions that make a site legible to AI agents: stable URLs, markdown twins, structured data, robots controls, and machine-readable discovery files. This page walks the Website Spec agent-readiness checklist item by item and shows where veezee.io stands. Every Live row links to the artifact itself, on this domain, fetchable right now.

Current score: the one required item, 8 of 9 recommended items, and 6 of 10 optional items are live. The rows below say exactly what is not live and why.

Required#

ItemStatusProof
Stable URLsLiveURLs are public contracts. Renamed pages keep serving as redirects (/twitter-api-for-ai-agents), and every published path is listed in /sitemap.xml.
ItemStatusProof
Agent readiness overviewLiveThis page.
/llms.txtLive/llms.txt: a curated index of the whole corpus.
Per-page MarkdownLiveAppend index.md to any docs URL, or send Accept: text/markdown. Try /docs/index.md.
robots.txt for AI crawlersLive/robots.txt names GPTBot, ClaudeBot, CCBot, Google-Extended, PerplexityBot, and more, each with an explicit allow.
Structured dataLiveJSON-LD (SoftwareApplication, Organization, Offer, BreadcrumbList) ships inline in every page. View source on / or /pricing.
Machine-readable formatsLive/product.json, /recipes.json, /openapi.json, /proof-feed.json.
HTTP Link headersLiveEvery page response carries a Link header naming /openapi.json as service-desc; the home page adds alternate links to /llms.txt and /index.md. Check with curl -sI https://veezee.io/.
Agent Skills discoveryLive/.well-known/agent-skills/index.json, backed by the packs at /docs/skills.
DNS-AIDNot yetThe _index._agents and _mcp._agents HTTPS records are drafted; DNS changes ship through a manual approval gate. Every artifact on this page is discoverable over HTTP today.

Optional#

ItemStatusProof
/llms-full.txtLive/llms-full.txt: the whole docs corpus in one fetch.
Content SignalsLiveContent-Signal: search=yes, ai-input=yes, ai-train=yes in /robots.txt.
Web Bot AuthNot applicableIt defines how bot operators sign their requests. A content site has nothing to publish, and we serve signed and unsigned bots the same content.
MCP and tool discoveryLive/.well-known/mcp.json and /.well-known/mcp-server-card.json, pointing at the live servers on mcp.veezee.io.
A2A agent cardLive/.well-known/agent-card.json. Veezee does not run an A2A server; the card points A2A-aware crawlers at the MCP surface.
Agentic Resource DiscoveryLive/.well-known/ai-catalog.json, advertised by the Agentmap line in /robots.txt.
NLWebNot plannedMCP already gives agents a queryable interface with real auth and per-call pricing. An /ask endpoint would duplicate it.
WebMCPLiveThe forms on /upgrade and /manage are declared as WebMCP tools (toolname and tooldescription attributes, plus imperative registration where fields are sensitive). Nothing auto-submits.
OKF bundleNot plannedThe corpus already ships as Markdown: per-page index.md twins and /llms-full.txt.
SchemamapNot plannedIt indexes per-resource .jsonld endpoints. Our JSON-LD ships inline in every page, so there are no .jsonld endpoints to index.

Why this page exists#

Veezee sells LinkedIn, Reddit, and X data to AI agents, so the site is built agent-first: an agent should be able to discover, evaluate, connect, and pay with no human in the loop except the payment itself. The conventions above are how an agent finds its way in. If we are missing one you rely on, tell us: hello@veezee.io.