Hosted Agent Policy URLs: When AgentGate Serves Your File
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
A hosted policy URL is an AgentGate Pro feature: instead of serving agent-policy.json from your own origin, AgentGate serves the document for you at a hosted address. It suits owners whose platforms make adding a /.well-known/ file genuinely hard, and owners who want the policy's home managed beside its change history. The trade-off is real and should be chosen knowingly: the spec's discovery model assumes the file lives on the origin it describes.
What is a hosted policy URL?
It is your policy document — the same generated, validated JSON — served from AgentGate's infrastructure under a public page that also presents the document's conformance summary and validation status, with a shareable result card. The generator already offers the pattern in miniature on the free tier: a generated policy can receive a public AgentGate page, reachable through its unguessable link and revocable from the result screen. Pro hosting makes that arrangement the policy's standing home rather than a by-product. The document's content is unchanged; what changes is the address, and therefore the discovery story around it.
The honest trade-off
Self-hosting's strength is the envelope principle from the publishing guide: terms served from the domain they govern, discoverable at the one address every agent checks first. A hosted URL steps outside that pure model — the document lives at an address an agent must be told, by your site, your documentation, or the operator relationship. For owners in genuine platform constraints — a website builder that forbids well-known files, a legacy stack where the change queue is measured in quarters — that cost buys the entire benefit of having a policy at all: written, validated, public, dated terms, versus none. The comparison is never hosted versus self-hosted in the abstract; it is hosted versus absent, for the owners who face it.
Who hosting suits, and who it does not
Hosting suits: small sites on restrictive builders; owners mid-migration who need terms published before the new platform lands; teams that value the managed change history and a single policy home across experiments. It does not suit: owners whose platforms serve a static file trivially (self-host — the envelope is worth more than the convenience); regulated postures whose examiners will ask why the boundary statement lives on a third party's domain; and fleets whose discovery strategy depends on strict well-known conformance across many origins. The pricing page states the feature's terms plainly — hosted policy URLs ride with Pro, alongside the batch API — and the generator's free public-page option lets any owner trial the shape before paying for the standing version.
Running a hosted policy well
Three practices keep a hosted policy honest. Point at it from home: link the hosted document from your own site's agent-facing places — footer, developer page, terms cross-reference — so the discovery gap is bridged by your own signposting. Keep the document identical in discipline: same generation, same validation, same review dates; hosting changes the address, never the standards. Plan the graduation: if the platform constraint lifts, move the file home to the well-known path, keep the hosted page pointing at the move, and tell your named operators — address changes are the policy equivalent of a domain migration, handled with the same care and notice.
Worked example: a builder-hosted boutique lives at a hosted URL, then graduates
Fictional example. Alba Ceramics, a fictional studio pottery selling through a website builder that permits no custom well-known files, launched its policy at a hosted URL on Pro: store-pattern rules, conditional catch-all, checkout fenced, the hosted page linked from the shop's footer and its terms page. For 14 months the arrangement did full duty — 5 operator enquiries arrived via the file, 2 becoming named rules. When Alba migrated to a platform with file control, graduation took one sprint: the identical document republished at /.well-known/agent-policy.json, the hosted page updated to point home, both named operators emailed. Total duplicated effort across the whole story: near zero — because the document, its decisions, and its review history had been real from the first day, at whichever address they lived.
The hosted URL checklist
- Choose it for the real reason. A platform constraint or a managed-home preference — not avoidance of a ten-minute file placement you can actually do.
- Signpost from home. Link the hosted policy from your own site's footer, docs, and terms, so discovery survives the address.
- Hold the document to full standards. Generated, validated, dated, reviewed — hosting changes the address, never the discipline.
- Keep the exit open. The document and its history should be exportable and movable; custody questions are answered before they are urgent.
- Graduate when you can. When the constraint lifts, republish at the well-known path and point the hosted page home.
Keep reading
What Is the agent-policy.json File? · How to Write an agent-policy.json File, Step by Step · What Is an Agent Access Policy (v0.1)? · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
Is a hosted policy the same document as a self-hosted one?
Content-wise, yes: the same AGENT-POLICY v0.1 JSON, produced by the same generator and held to the same validation. What differs is the serving address and therefore discovery: self-hosted files are found at the origin's well-known path by default; hosted files are found where they are signposted. The terms an agent reads, once it arrives, are identical in kind.
Will agents find a hosted policy automatically?
Not by the pure well-known mechanism — that is the trade-off stated plainly. Discovery is bridged by signposting: links from your own site, your documentation, your terms, and direct communication with operators. For many small sites that bridge carries all the traffic that matters; owners for whom automatic discovery is the point should self-host.
What does hosting cost?
Hosted policy URLs are a Pro-tier feature — Pro is $49 per month and also includes the batch validation API. The free tier includes a lighter version of the pattern: generated policies can receive a public AgentGate page via an unguessable, revocable link. The pricing page carries the current terms for both.
Can I move from hosted to self-hosted later?
Yes, and the pattern is designed for it: republish the identical document at your origin's well-known path, update the hosted page to point at the canonical home, and notify named operators. Nothing in the document changes except its address and, in the site field's spirit, its home — the decisions and history carry over whole.
Why would AgentGate offer hosting if self-hosting is the spec's model?
Because the alternative for a constrained owner is not self-hosting — it is no policy. A format that only serves owners with full platform control abandons exactly the small sites whose agent terms are most often guessed at. Hosting is the pragmatic bridge: real terms, publicly served, today — with graduation to the well-known path kept open and encouraged.
Generate a policy — free · Validate a policy · What an agent access policy is