Publishing Your First Agent Policy: a Launch Guide
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
Your first agent policy is an afternoon's work, and most of it is deciding, not writing. The launch sequence: pick the published sample closest to your posture, make the five decisions (default, named agents, action split, terms, pace), build the file with the free generator, validate it, publish it at /.well-known/agent-policy.json, and fetch it once the way an agent would. This guide is the sequence with the judgement calls marked.
What does a first policy need to be?
Honest, valid, and small enough to maintain. Honest: its verdicts describe your real posture, including a refusal where refusal is the truth. Valid: it passes the five conformance rules, because an invalid first file teaches every reader — agents, operators, your own team — that the document is decorative. Small: a default, a catch-all, and the named rules you can already justify, because every rule you publish is a decision you will review quarterly. The samples prove the range: the bank's entire policy is a posture and an empty list; the store's is three rules. Yours will sit between them, and the examples guide is the tour of that territory.
The five decisions, in launch order
One — the default. If you remember nothing else: strangers get allow, block, or conditional. When genuinely unsure, conditional is the launch default for most sites — it buys a quarter of observation without refusing anyone permanently. Two — the agents you already know. Partners, known quantities, known problems: each gets a rule expressing the relationship as it stands today, not as it might evolve. Three — the action split. Your journey's looking verbs permitted, its committing verbs refused, per the split pattern. Four — the terms. Free where access is marketing, paid-tier only where a tier exists, contact where negotiation is the honest state. Five — the pace. The samples' ladder (60/30/10) until your own traffic teaches you better.
Build, validate, publish — the mechanical hour
Build with the generator: the questionnaire is the five decisions wearing form fields, and the output cannot omit a required field or misspell a domain value. Validate the output anyway — the habit matters more than this instance — and read the report's warnings with the warnings discipline: fix accidents, own intentions. Publish at the well-known path on the origin the file names, as application/json, reachable logged-out; the publishing guide lists the failure modes, of which the login-wall interception is the one that bites first-timers with real platforms. Then the agent's-eye check: fetch the live URL from a clean session and validate that body. Only now does the policy exist.
The first quarter: what to expect and do
Expect quiet, then signal. The contact address collects its first operator enquiries — answer them at business speed, and convert resolutions into named rules while the context is warm. Watch whichever analytics you already keep for the well-known URL's first appearances in agent-shaped traffic. Calendar the first review at 90 days with the four questions from the cadence guide, and resist mid-quarter tinkering that is not event-driven: your first file's job is to be a stable instrument you can learn from, and stability is what makes the first review's evidence readable. Announce proportionately — a line in your developer or partner communications, the URL in your terms' cross-references — because operators cannot honour terms they never learn exist.
Worked example: a bookshop launches in one afternoon
Fictional example. The Bound Page, a fictional independent bookshop with 18,000 titles online, launched on a Tuesday. Starting sample: the store. Decisions in 50 minutes: conditional default; 2 named rules (a shopping agent welcomed on the split at 40 per minute, free terms — the shop treats agent shoppers as demand; a reading agent at 30, attribution required); catch-all conditional at 10; checkout, submit-form, and crawl-full-site disallowed everywhere; data-use terms refusing resale and cover-image training. Build and first validation: 20 minutes, one overlap error (search in both lists of the draft catch-all) fixed on the spot. Publish and live-check: 15 minutes. First operator enquiry: day 9. First review: calendared before the file went live, because the owner had read the cadence guide first.
The launch checklist
- Start from the closest sample. Bank, blog, or store — change the decisions, keep the structure.
- Make the five decisions. Default; known agents; action split; terms; pace — in that order, in one sitting.
- Generate, then validate. The generator for construction, the validator for proof — warnings decided, errors zero.
- Publish and fetch like an agent. Well-known path, JSON, logged-out fetch, live copy validated.
- Calendar the first review before announcing. Ninety days out, with the contact staffed from day one.
Keep reading
Agent Policies for Multiple Websites: Running a Fleet · Agent Policy for Agencies: Managing Client Policies · What Is an Agent Access Policy (v0.1)? · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
How long does launching a first policy take?
A focused afternoon for most sites: under an hour of decisions, an hour of building and validation, minutes to publish, and a quarter-hour of live checking. The scarce input is not time but the five decisions' honesty — owners who arrive knowing their posture finish fastest; the generator's questionnaire doubles as the decision worksheet for those who do not.
What if we are not sure of our posture yet?
Publish the sure parts. A conditional default with a fenced catch-all is a legitimate, complete posture — it says 'ask us' while the organisation learns — and it is vastly better than silence, because the learning then happens through a staffed door instead of through agents guessing. Uncertainty is a reason for conditional, not for delay.
Do we need legal review before launching?
That is your organisation's call, proportionate to your sector: regulated and public bodies route the file through their normal publishing governance, as the vertical guides note. What legal review should not become is a reason the file never ships — the document is a declaration of posture, explicitly not legal advice, and its terms can be revised the day better counsel arrives.
Should we announce the policy?
Yes, in the channels counterparties read: partner and developer communications, the terms-of-service cross-reference, a line wherever your API or data licensing is described. Discovery via the well-known URL handles agents; announcement handles the humans who operate them — and first enquiries arrive faster when both are done.
What is the most common launch mistake?
Publishing a draft that was never live-checked: the file validates beautifully on disk while the well-known URL serves a login page, a stale copy, or nothing. The agent's-eye fetch — logged out, exact URL, validate the returned body — is the launch step that separates having a policy from believing you have one.
Generate a policy — free · Validate a policy · What an agent access policy is