A practical readiness report a business can act on.

# Agent Readiness Report: Example SaaS

Score: 54/100
Grade: D
Projected score after package outputs: 94/100

## Site Evidence
- Homepage title: Example SaaS
- Homepage description: Workflow software for operations teams.

## Highest-priority fixes
- Publish /llms.txt and /llms-full.txt.
- Add /.well-known/agent.json.
- Link support, docs, pricing and status from agent-readable files.

## Package outputs
- Agent context file
- Full agent context file
- Agent manifest
- Publishing guide

# API Agent Readiness Plan

## Developer readiness checklist
- Link canonical API docs from llms.txt and llms-full.txt.
- Publish or link OpenAPI.
- Mark auth requirements, scopes, rate limits and error states.
- Separate read actions from write actions.
- State where human approval is required.

## Agent-safe examples
- Prefer published examples.
- Do not invent endpoints, scopes or auth behaviour.

# Commerce Readiness Plan

## Buying path and review boundaries
- Describe what a human can buy and what they receive after payment.
- Keep checkout language clear and current.
- State that purchase, account changes and sensitive actions require human approval.
- Keep support, refund and delivery expectations visible near pricing.

## Structured commerce checklist
- Product names and prices are current.
- Refund, support and delivery terms are linked.
- Agent instructions do not imply autonomous purchases without human approval.

# Web3 Agent Readiness Notes

## Safe agent behaviour
- Explain what is live from published docs only.
- State network, asset, wallet and support boundaries clearly.
- Do not imply custody, investment advice or unsupported settlement rails.

## Recommended files
- llms.txt
- llms-full.txt
- .well-known/agent.json
- agent-safe claims checklist