tp tate@programs sample report
tate@programs ~/reports/agent-readiness-sample fictional public-surface proof packet

sample proof packet

What an agent-ready website report should make obvious.

This fictional sample shows the shape of a fixed $750 outside proof packet: public discovery files, agent-readable actions, schema and sitemap evidence, the authorization boundary, and the first patch order.

read sample scope packet send surface
example
fictional shop
scope
public only
output
patch order

sample report

Pattern Shop Agent Readiness Readback

fictional surface

score

62 / 100

Good human site and partial machine-readable posture, but not yet strong enough for a client-facing agent-readiness claim.

scope

Public no-login

Reviewed homepage, product sample, policy pages, sitemap, discovery files, public forms, and visible structured data.

ship call

Proof after patches

Use internally now. Publish the readiness claim after the missing discovery files and action semantics are patched.

Positive Evidence

  • `/llms.txt`: reachable and points to product, policy, and support pages.
  • Sitemap: reachable and includes product, collection, FAQ, shipping, returns, and contact pages.
  • Product schema: sampled product page exposes Product, Offer, image, price, currency, and availability.
  • Policy pages: shipping, returns, privacy, terms, and support pages are reachable from the footer.
  • Contact path: public form has stable labels and a visible support fallback.

gap

Missing agent index

`/agents.json` and `/agents.md` return 404, so an agent has no canonical summary of supported tasks or boundaries.

gap

No MCP card

`/.well-known/mcp/server-card.json` is absent, so any tool-capability claim still needs a separate proof artifact.

gap

No agentic sitemap

`/sitemap_agentic_discovery.xml` is absent, which makes machine-readable task discovery weaker for launch partners.

Priority Patch Order

  • P0: Add `/agents.json` with allowed public tasks, disallowed tasks, support fallback, and clear no-payment/no-order boundary.
  • P0: Add an agentic sitemap that lists product, collection, policy, support, and contact paths with last-modified dates.
  • P1: Add MCP server-card or explicit "no public MCP server" statement so partner reviewers do not guess.
  • P1: Add schema for MerchantReturnPolicy and shipping details on product or policy pages.
  • P1: Tighten public form semantics with stable labels, button names, error states, and a predictable success state.
  • P2: Add a short agent-readiness changelog line to the public docs or footer so the claim has dated evidence.
public claim Hold until P0 patches land
client handoff Attach after re-check
private proof Only with authorized scope

boundary

The point is to prove the claim without touching private systems.

A public agent-readiness report should make three things inspectable: what a machine can discover, what actions are actually allowed, and where public proof stops. The packet should not require a customer login, cart mutation, checkout creation, payment, order lookup, or guessing private endpoints. 

deliverable:
  public discovery readback
  action boundary
  schema and sitemap notes
  WebMCP / Lighthouse notes
  patch order
  re-check after changes