Free plan

← All guides

Let Agents Browse but Not Check Out: the Split Rule

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

The short answer

The browse-but-not-checkout pattern is one rule with a deliberate split: browse, read, search, and shop in permitted_actions; checkout, submit-form, and api-call in disallowed_actions. The agent can do everything a good shop assistant does — find, compare, assemble — and nothing that commits money or changes state. It is the single most useful rule shape in the AGENT-POLICY format, and the published store sample is built from it.

Generate your policy — free · Validate an existing one

What is the split rule?

It is a line drawn between looking and committing, expressed in the vocabulary's own verbs. Everything on the permitted side is reversible and information-shaped; everything on the disallowed side spends, submits, or mutates. The line is not specific to retail: a travel site runs the same split with book on the refused side, a SaaS site with api-call, a publisher with crawl-full-site. Once you see the format as a machine for drawing this one line at different places for different agents, most policy design becomes deciding where your line sits — the subject of the action lists guide.

Anatomy of the split, field by field

Take the store sample's best rule as the template. identifier: a named shopping agent. allowed: yes — the split is a welcome, not a refusal. Permitted: the four looking verbs. Disallowed: the three committing verbs. commercial_terms: paid-tier — the looking is worth charging for at this pace. rate_limit: 60 requests per minute — working speed. data_use_terms: catalogue data for price comparison and shopping assistance only, no resale, no training on product images — the after-life fenced as carefully as the visit. Every field pulls in the same direction. When you adapt the split, adapt it whole: a rule that permits the looking verbs but forgets the data-use fence has drawn half a line.

Where to draw the line on your site

Walk your own customer journey and mark the first irreversible step. For a store it is payment. For a booking business it may be the reservation itself, if reservations hold scarce inventory — in which case book joins the refused side and the permitted side becomes research-and-quote. For a lead-generation site, the form submission is the product, so submit-form may be the one committing verb you permit — for named agents, with terms. The split is a decision about your business wearing the format's clothes; the vertical guides for booking sites and online stores draw it for their industries, and the shopping decision guide argues the retail case in full.

The hand-back is the feature

Owners sometimes read the split as a half-measure — the agent does 90% of a purchase and stops. Read it instead as the format's central courtesy: the agent stops exactly where a thoughtful human assistant would stop, at the moment of commitment, and presents its work. The cart it built is the deliverable. Users experience this as their agent saying "here is the best option I found, at this store, ready when you are" — with the store's policy as the reason the pause exists. A well-drawn split therefore is not agent access diminished; it is agent access shaped into the form your customers would have asked for.

Adopt the split early and it also becomes your organising answer to every future agent question, because new requests sort themselves against the line you have already drawn. May this new agent see our outlet pricing? Looking — permitted side, price it in the terms. May it reserve stock? Committing — refused side, or a named negotiation. May it message customers about their orders? State-changing — refused, until a partner case is argued. Teams without a drawn line re-litigate philosophy per request, slowly and inconsistently; teams with one answer most questions in a sentence and save their deliberation for the genuinely new. That operational calm is the split's least advertised benefit, and for busy owners it may be the largest.

Worked example: an appliance retailer's split, measured over a quarter

Fictional example. Voltaic Appliances, a fictional retailer selling 850 large appliances, runs the split across 3 rules: 2 named shopping agents at yes, 50 requests per minute, paid-tier terms; the catch-all at conditional, 10 per minute. checkout, submit-form, and api-call are disallowed everywhere. Over its first quarter, agent sessions built 1,140 carts; the retailer's analytics attributed 388 completed orders to customers returning to those carts. Its returns desk, meanwhile, handled 0 agent-originated orders — there were none — against a background of 61 ordinary mis-orders (wrong size, wrong fuel type) placed by humans in the same period. The owner's summary at quarter-end was one line: the agents are our most careful shoppers, because our policy only lets them be.

Drawing your split in five steps

  1. Walk the journey. Trace an agent's path through your site and mark the first irreversible step.
  2. Permit the looking verbs. browse, read, search, and shop (or your industry's equivalents) go in the permitted list.
  3. Disallow the committing verbs. checkout, submit-form, api-call — and book where reservations commit you.
  4. Fence the after-life. Data-use terms that match the split: comparison and assistance, not resale or training.
  5. Mirror it in the catch-all. Strangers get the same line at a slower pace and a conditional verdict — never a weaker fence.

Keep reading

How to Charge AI Agents for Access to Your Site · Conditional Access: Making Agents Contact You First · How to Tell AI Agents What They May Do · Spec samples · Conformance · Pricing · All guides

Frequently asked questions

Is shop without checkout actually useful to an agent?

It is the core of agent-assisted shopping. Comparison across a catalogue — prices, specifications, availability — is the labour users delegate; the purchase itself is a moment most users want to see before it happens. An agent that returns a built cart with a recommendation has done the work. The split makes that workflow the permitted shape instead of a failed checkout.

Can the agent hold items in a cart indefinitely?

Cart behaviour is your store's own mechanics — expiry, stock holds, and session rules belong to your platform, not the policy. The policy governs the agent's permission to perform the shopping actions. If your carts expire in an hour, agent-built carts expire in an hour; the declaration does not override your store's rules of the house.

Should the catch-all get the same split?

The same line, at a stricter posture: typically conditional instead of yes, a lower rate limit, and contact or free terms rather than a negotiated tier. What the catch-all should never get is a weaker fence — the committing verbs stay disallowed for strangers even more firmly than for named partners.

What about booking sites — is book the checkout?

Functionally, yes: booking is the committing verb for travel, appointments, and reservations. Booking sites draw the split with book on the disallowed side and research verbs permitted, or make book conditional per agent. The travel and booking guide works the pattern for that industry in full.

Does the split need paid-tier terms?

No. The sample pairs the split with paid-tier because that store prices catalogue access; a store treating agent shoppers purely as demand can run the identical split on free terms. The split is about actions, not price — terms are chosen on their own logic, per the commercial terms guide.

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

← Back