The generic/* Rule: Your Policy's Catch-All, Explained
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
generic/* is the catch-all identifier in an agent policy: a rule addressed to it speaks to every agent that no other rule names. It turns your default_policy from a bare verdict into a full rule — with action lists, commercial terms, a rate limit, and data-use terms — for the entire unnamed world. The store sample holds its catch-all at conditional, 10 requests per minute, with checkout refused: strangers are answered in detail, not just in principle.
What is the catch-all rule?
It is a normal per-agent rule whose identifier happens to match everyone unlisted. Identifiers are normally specific — one vendor's one product. generic/* is the deliberate exception, the registry's seventh entry, defined as "any agent not named elsewhere". An agent reading your file checks for its own identifier first; finding none, it reads the catch-all as its rule. That makes the catch-all the most-read rule in most policies, because most agents visiting most sites are not the famous six.
Catch-all versus default: why have both?
Because they carry different amounts of information. default_policy is a single value — allow, block, or conditional — with no room for actions or terms. The catch-all is a full rule: it can say conditional, and when you contact us, here is the shape of the deal; meanwhile know that checkout is refused and the pace is 10 a minute. Sites that publish both layers get a coherent stranger policy: the default states the posture, the catch-all states the conditions. Sites that publish neither named rules nor a catch-all — a default alone — still have a valid policy; the bank sample is exactly that. But the moment you care how strangers behave rather than merely whether, the catch-all is where the caring goes, as the rules guide sets out.
Writing a catch-all that earns its place
Three decisions define a good catch-all. The verdict usually mirrors or softens the default: conditional is the common choice, converting unknown traffic into contact. The pace is the ladder's bottom rung — the samples' 10 requests per minute against 30 and 60 for named agents — because strangers have no track record. The refusals should be the irreversible verbs: checkout, submit-form, api-call, crawl-full-site belong in the catch-all's disallowed list almost regardless of the rest of your policy, because whatever an unknown agent may eventually negotiate, it should not find those granted by the rule written for everyone. The pattern generalises the store sample's approach and is worked for a specific shape of site in browse but not check out.
When the catch-all becomes a named rule
The catch-all is also a nursery. An agent that arrives under it, contacts you as the conditional verdict invites, and agrees terms graduates: you write it a named rule with its own identifier, verdict, and limits, and from then on it reads that instead. Nothing in the format tracks this for you — it is a policy-maintenance habit, and a good reason to keep the contact address staffed and the review cadence real, as covered in how often to update your policy. Over time a healthy policy's named rules grow out of its catch-all traffic; the catch-all itself stays, permanently, for the next stranger.
Treat the catch-all, finally, as the rule your future self will be most grateful for. Every other rule in the file was written for a known counterparty in a known moment; the catch-all is written for the agent that does not exist yet, arriving on a day when nobody is watching, asking a question nobody anticipated. A considered catch-all answers that arrival with the house's standing wisdom instead of its absence. When the ecosystem shifts — and in this ecosystem it shifts quarterly — the catch-all is also the shock absorber: revise one rule and every unnamed relationship updates at once, while the named ones keep their negotiated shape. It is the smallest rule in most files and the one doing the most work per line.
Worked example: a language school's catch-all graduates two agents
Fictional example. Casa del Idioma, a fictional language school selling courses in 6 languages, launched with a lean file: a conditional default and a single generic/* rule — conditional, browse and read named as the subjects of any future grant, submit-form and checkout disallowed, 10 requests per minute, contact terms. In two terms, 8 operators made contact through it. Two — a course-comparison agent and a tutoring marketplace's agent — became named rules at yes, 30 per minute, free terms. Three were declined and stayed under the catch-all. Three never replied to the school's answer, which is also information. The catch-all cost the school one rule's worth of writing and did the work of a part-time partnerships inbox.
The catch-all checklist
- Always publish one. Even a lean policy gains a full stranger rule from a single
generic/*entry. - Mirror the default's posture. Let the catch-all's verdict agree with
default_policy, then add the detail the default cannot carry. - Set the slowest pace. Strangers get the bottom rung of your rate ladder.
- Refuse the irreversible. Put
checkout,submit-form,api-call, andcrawl-full-sitein its disallowed list. - Graduate the known. When a catch-all agent negotiates terms, promote it to a named rule.
Keep reading
The signature Field in agent-policy.json: Why It Is null · Versioning an Agent Policy: policy_version and last_updated · How to Tell AI Agents What They May Do · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
Is generic/* a real identifier or a placeholder?
It is a real registry entry — the v0.1 registry's seventh identifier, defined as the catch-all matching any agent not named elsewhere. A rule addressed to it is a normal rule in every respect: verdict, action lists, terms, rate limit, and data-use terms all apply.
Does the catch-all override default_policy?
It refines it for unnamed agents. An agent with no named rule reads the generic/* rule as its rule; the default remains the fallback behind everything and the posture statement for the file. In practice the two should agree in verdict so the file reads consistently at both levels.
What if I publish no catch-all rule?
Your policy is still valid — the samples include one with an empty agents list. Unnamed agents then get only the default verdict, with no stated actions, terms, or pace. That is a legitimate choice for a block posture, and a missed opportunity for any site that wants strangers handled in detail.
Can generic/* be set to no while the default is allow?
Yes. The combination says: named agents and the general default are open, but the unnamed mass is refused except where a rule grants it. It is an unusual layering — the reverse of the common pattern — but the format permits it, and a few owners use it to force every real relationship to be named.
Does an agent ever read both its named rule and the catch-all?
No. Matching is exclusive: an agent reads the rule addressed to its own identifier if one exists, and the catch-all only when none does. That exclusivity is why duplicate identifiers are an error and why the catch-all never dilutes a named agent's negotiated terms.
Generate a policy — free · Validate a policy · What an agent access policy is