Every page links to a complete map of what this site can do for an agent — discovery files, API specs, runtime tools, and content-signal preferences — published against open standards (RFC 8288, RFC 9727, llmstxt.org, IAB Content Signals, MCP). Crawlers and agents can fetch each artifact directly from the URLs below.
Concise sitemap of every public destination in the format proposed by llmstxt.org. Optimized for a single LLM read — capability statement, federal track, commercial track, contact, insights, and links to the deeper artifacts below.
Open llms.txt →Concatenated full text of every public page plus the entire insights archive, generated at build time. Use this when the model needs the actual page content, not just a sitemap.
Open llms-full.txt →Linkset that enumerates each /api/* endpoint with a service-desc pointer to its OpenAPI 3.1 JSON spec, a service-doc pointer to the HTML doc page, and a health-check URL.
Open .well-known/api-catalog →Cloudflare agent-skills-discovery-rfc v0.2.0 index. Six skills covering scheduling, federal and commercial intake, capability-statement download, availability check, and the chat agent. Each entry carries a SHA-256 of its markdown body.
Open .well-known/agent-skills/index.json →MCP SEP-1649 discovery stub for the Truvisory chat agent. Currently advertises a plain JSON request/response transport at /api/chat; a full MCP JSON-RPC upgrade is on the roadmap.
Open .well-known/mcp/server-card.json →Google A2A protocol discovery for agent-to-agent interoperation. Declares the chat endpoint, supported transports (JSONRPC + HTTP+JSON), capabilities, and seven skills (chat, scheduling, federal and commercial intake, capability download, availability, ask-agent).
Open .well-known/agent-card.json →Signed Ed25519 JWKS for IETF Web Bot Auth. Verifiers fetch this directory to confirm outbound bot/agent requests from this site are genuine. Each response is signed per RFC 9421 with the same key it advertises, proving operator control.
Open .well-known/http-message-signatures-directory →| Method | Path | Purpose | Specs |
|---|---|---|---|
| GET | /api/availability | List open 30-minute discovery-call slots, Mon–Fri Mountain Time. | OpenAPI → HTML docs → |
| POST | /api/chat | Send a message to the Truvisory agent. sessionId carries memory across turns. | OpenAPI → HTML docs → |
| POST | /api/book | Confirm a chosen slot on the founder calendar; returns a Google Meet link. | OpenAPI → HTML docs → |
| POST | /api/contact | Submit a federal or commercial inquiry. Door-routed; ≥10-char message required. | OpenAPI → HTML docs → |
If the browser supports the WebMCP draft via
navigator.modelContext
(Chrome 142+ Canary as of 2026), Truvisory registers four tools at
page load. Agents can call them in-place without negotiating a
transport.
Probe from DevTools:
navigator.modelContext.getTools().then(t => console.log(t.map(x => x.name)))
Link response header carries pointers to every discovery artifact below from any page.
/.well-known/api-catalog returns an application/linkset+json document referencing each OpenAPI spec.
/llms.txt and /llms-full.txt follow the proposed format for LLM-optimized site overviews.
robots.txt declares ai-train=yes, search=yes, ai-input=yes — maximum visibility for a marketing surface.
/.well-known/agent-skills/index.json plus per-skill markdown bodies, each verifiable by SHA-256 digest.
/.well-known/mcp/server-card.json publishes the chat agent as a discoverable MCP server (transport upgrade pending).
/.well-known/agent-card.json publishes the Truvisory AI agent for agent-to-agent discovery — name, version, supported transports, capabilities, and seven skills.
/.well-known/http-message-signatures-directory publishes a signed Ed25519 JWKS so receiving systems can verify outbound bot/agent traffic from this site.
SVCB records under _index/_a2a/_skills/_mcp._agents.truvisory.com let DNS-aware agents discover the chat endpoint, A2A surface, agent-skills index, and MCP server card without an HTTP request. Zone is DNSSEC-signed.
Cloudflare's Markdown for Agents is also
enabled on this zone — sending Accept: text/markdown
to any URL returns the page as Markdown, transformed at the edge.
