Free plan

← All guides

Conditional Access: Making Agents Contact You First

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

The short answer

conditional is the AGENT-POLICY value that means contact the owner first. It appears in two places: as default_policy, where it pauses every unnamed agent, and as a rule's allowed value, where it pauses one named agent. It is neither yes nor no — it is the format's way of turning agent access into a conversation, using the owner.contact in your file's header as the door. AgentGate's own published policy uses it as the default.

Generate your policy — free · Validate an existing one

What is conditional access?

It is a published pause. An agent reading a conditional verdict learns three things: it is not refused; it is not yet permitted; and the next step is a human conversation through a stated address. The spec defines the value identically at both levels — the default and the rule — and deliberately defines no real-time negotiation protocol around it: no handshake format, no approval token, no machine-readable grant comes back. The conversation happens the way business conversations happen, and its outcome is recorded the way the format records everything: by editing the file, giving the agent a named rule with its agreed verdict, and moving last_updated.

Where conditional does its best work

Three situations, above all. The stranger problem: as a default or catch-all posture, conditional sorts unknown agents into an inbox instead of a binary guess — the use the default guide recommends for most first policies. The valuable-access problem: where access is worth negotiating — bulk data, transactional rights, premium pace — conditional on those rules starts the negotiation the charging guide finishes. The not-yet problem: an agent you expect to allow eventually, once you have seen its operator's answers, waits at conditional in the meantime — visible in your file, neither granted nor refused, with the relationship's state honestly published.

The discipline conditional demands: a staffed door

Conditional is the only verdict that creates work for the owner, and it creates it in the owner's own inbox. An unmonitored owner.contact converts every conditional in your file into a refusal by neglect — ruder than an honest block, because it wastes the operator's effort on a door nobody opens. The discipline is modest but real: the address reaches a person; enquiries get an answer within days, not months; outcomes get written back into the file as named rules. Owners who cannot staff the door should choose allow or block and mean it — the catch-all guide shows how the posture layers either way. Conditional is a promise to talk; publish it only if you keep promises.

What conditional is not

It is not a rate limit (that is rate_limit's job), not a payment demand (that is commercial_terms: contact or paid-tier, its close cousins), and not a soft block with plausible denability — agents and operators read it as the genuine intermediate state it is, and judge owners by what happens next. It is also not permanent by nature: a healthy policy's conditionals resolve over time, in both directions, as relationships form or fail to. A file whose every rule has sat at conditional for a year is telling the truth about its owner, one way or another.

Conditional has one more use that deserves naming: it is the format's way of saying not yet without burning the bridge. A flat refusal teaches an operator to route around your site permanently; a conditional teaches them your door exists and is staffed. In an ecosystem where today's unknown agent is next year's default shopping companion for half your customers, that difference compounds. The owners who run conditional well describe the same experience a year in: the inbox it created became their earliest map of the agent economy — who is building what, for which users, at what scale — information their competitors, sitting behind blocks or blank silence, simply never received. The pause, staffed properly, is an intelligence asset wearing a verdict's clothes.

Worked example: a wholesaler runs its whole front door at conditional

Fictional example. Hartley Industrial Supply, a fictional B2B wholesaler with 9,500 trade products, publishes a conditional default and a conditional catch-all, with just 2 named rules — both long-standing partners at yes. Every other agent relationship begins as an email to the address in the header. The wholesaler's operations lead answers within 2 business days with a 4-question note (operator identity, purpose, expected volume, data needs). In the policy's first year: 17 enquiries, 9 became named yes rules with individual pace caps between 20 and 80 requests per minute, 5 were declined with reasons, and 3 went unanswered by the enquirer after the questions arrived. The file grew from 3 rules to 11 — conditional doing exactly its designed work as the front door of a considered business.

The conditional checklist

  1. Point it at a human. owner.contact must reach someone who answers agent enquiries as part of their job.
  2. Set a response rhythm. Days, not months — conditional is a promise to talk, kept at inbox speed.
  3. Ask standard questions. Identity, purpose, volume, data needs: the same four, every time, so answers stay comparable.
  4. Write outcomes into the file. Every resolved conditional becomes a named rule — yes with terms, or no with the refusal on record.
  5. Audit the pending pile. Review unresolved conditionals quarterly; a growing pile means the door is understaffed, not that agents are pushy.

Keep reading

How to Block All AI Agents (and Say So Clearly) · How to Welcome AI Agents on Your Site · Agent Access Policy Examples · Spec samples · Conformance · Pricing · All guides

Frequently asked questions

What should an agent do when it reads conditional?

Pause and contact the owner through the address in the policy header — or have its operator do so — before operating. v0.1 defines no automated negotiation, so the conversation is an ordinary business exchange. Operating first and asking later is not a reading of conditional any owner accepts.

Is conditional a polite no?

It is not intended as one, and operators can tell the difference: an owner who answers and converts enquiries into named rules is running a door; an owner who never answers is running a wall with extra steps. The verdict's meaning is completed by the owner's behaviour at the contact address.

Can a rule be conditional while the default is allow?

Yes. The layers are independent. That combination says: the unnamed world is welcome, but this particular agent — perhaps because of the scale or kind of access it wants — should talk first. Per-agent conditional under an open default is the standard shape for premium-access conversations.

How long should an agent wait at conditional?

The format sets no clock, because the negotiation is deliberately out of band. Businesslike expectations apply: an enquiry unanswered after a couple of weeks is, in practice, an answer. Owners who value their conditional's credibility answer inside days — the credibility is the asset.

Does conditional pair with commercial_terms contact?

Often, but they are different fields: conditional governs permission (pause and ask), contact governs price (negotiate the basis). A rule commonly carries both for premium access. It can also carry conditional with free terms — permission needs a conversation, price does not — or yes with paid-tier terms, where the commercial step replaces the permission conversation.

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

← Back