Free plan

← All guides

Agent Policy for Government and Public-Sector Sites

Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team

The short answer

Government and public-sector sites exist to be used by everyone — increasingly including everyone's agents. The public-sector pattern is therefore the most open on this site: an allow default over public information, generous reading and search terms for the agents citizens send, and firm fences around the two things agents must not do on a citizen's behalf without governed authorisation — submit official forms and transact services. The policy is where a public body's agent posture becomes a matter of public record, which suits the sector.

Generate your policy — free · Validate an existing one

What is the public-sector posture?

Openness with a hard transactional edge. Public information — guidance, registers, statistics, service descriptions — is published at public expense for public use, and an agent reading it to help a citizen navigate a benefit or a deadline is the information doing its job through a new channel. Service transactions are the opposite case: a submitted form is a legal act by an identified citizen, and a public JSON file cannot carry that authorisation. The pattern grants the first wholesale and refuses the second by category, then uses named rules for the sector's real exceptions — data licensees, other public bodies, accessibility services.

Openness as the default's natural value

Most sectors choose their default by weighing risks; the public sector's default is substantially chosen for it by its mandate. Guidance that agents cannot read is guidance citizens with agents cannot use — an accessibility regression the sector should refuse deliberately if it refuses it at all. So: allow default, a catch-all rule granting the reading verbs plus search at a strong public pace, and data_use_terms that typically encourage reuse — many public bodies publish under open licences, and the policy is the agent-readable place to say the content carries one. Where statistics and registers are the product, download belongs in the welcome too, paced like a bulk service rather than refused like a scrape.

The transactional fence

submit-form and service-transaction verbs sit disallowed in every rule, with the reasoning stated in the notice: forms are legal submissions by identified persons, completed through the service's own channels. This is the healthcare pattern's logic in civic dress — the declaration must never be mistakable for an authorisation to act for a citizen. The fence also protects the body itself: an agent that submits ten thousand benefit forms has created a public-administration incident, and the clean published refusal is the body's first document in every review of how it happened. Accessibility exceptions — agents that act for citizens under formal assistance arrangements — are governed programmes, recorded like finance's exceptions: authorised elsewhere, described here.

Procurement, records, and the review habit

Public bodies keep records by culture, which makes the policy's maintenance artefacts natural fits: change history reads like a file note, the quarterly review joins the body's other publishing reviews, and the policy itself becomes part of the public record of how the body governs automated access to its services. One procurement note matters more each year: bodies buying digital services should expect vendors' agent postures to be equally declarable — a supplier whose own policy is a conforming, current file has answered the first agent-governance question before it is asked. The sector sets norms by publishing its own house in order.

Worked example: a municipal council's open file

Fictional example. The Municipality of San Esperanza, a fictional council serving 210,000 residents, publishes: allow default; catch-all granting browse, read, search, and download at 50 requests per minute under the council's open licence, stated in the data-use terms; submit-form and api-call disallowed in all 5 rules; named rules for the national statistics office (bulk download at 120 per minute under its data-sharing agreement) and for an accessibility charity whose reading agent receives a higher pace. The notice states that forms are legal submissions completed through council channels. In its first year the file was cited in 2 other councils' internal papers as their drafting model — public-sector policies compound in value because the sector copies its own best practice in the open.

The public-sector checklist

  1. Default to openness. Public information exists to be used; the allow posture states that as policy, not just practice.
  2. Say the licence in the terms. Open-licence status and reuse expectations belong in data_use_terms, where agents read them.
  3. Fence legal acts categorically. submit-form and service transactions disallowed in every rule, reasoning stated in the notice.
  4. Record governed exceptions. Data-sharing and accessibility arrangements as named rules, authorised through real programmes.
  5. Keep the file as a public record. Change history, dated reviews, published reasoning — the sector's habits applied to its newest document.

Keep reading

Agent Policy for Real Estate Sites · Agent Policy for Restaurants and Food Delivery · What Is an Agent Access Policy (v0.1)? · Spec samples · Conformance · Pricing · All guides

Frequently asked questions

Should a government site ever use a block default?

For specific sensitive services — law-enforcement-adjacent, safeguarding, certain registries — a block posture on that service's own origin can be the right call, argued the finance way. For a body's main public presence, block contradicts the mandate: the information was published for citizens, and citizens increasingly arrive through agents. Posture follows the service's nature, origin by origin.

Does an open policy create obligations for the body?

The spec's caution applies everywhere: the policy is a declaration, not legal advice, and conformance is not a legal opinion. Public bodies should clear the file through their normal publishing governance — legal, accessibility, records — exactly because it is a public statement of posture. That clearance is a strength: the file that survives it can be defended as policy, not treated as a web-team artefact.

How should open data downloads be handled?

As a service, not a leak. Where registers and statistics are published for reuse, grant download explicitly, pace it like infrastructure, and point bulk users at the body's data services in the terms. Agents doing legitimate civic and commercial work on open data are the open-data programme succeeding; the policy lets the body say so and shape it.

What about agents submitting forms for disabled citizens?

Assisted digital is a real and governed service category — arranged through the body's accessibility programmes, with consent and identity handled by design. The public policy should record such arrangements' existence, as it records other governed exceptions, while keeping the general fence intact: the exception's authority comes from the programme, never from the file alone.

Who should own a council's policy?

The digital service owner, with legal and records colleagues in the review — the pattern this site calls the policy's natural committee. In the public sector the file's audiences include other public bodies and the press, so its reasoning deserves the same editorial care as any published position.

Generate a policy — free · Validate a policy · What an agent access policy is

← Back