Commercial Terms for AI Agents: free, paid-tier, or contact
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
commercial_terms is the required field in every agent-policy rule that prices the relationship. It takes three values: free — no charge for operating under this rule; paid-tier — the owner offers a paid data or access tier, with details via the owner contact; and contact — negotiate before operating. It is set per rule, not per site, so one file can welcome readers free while charging shoppers — the published store sample does exactly that.
What are commercial terms, in this format?
They are the smallest possible price tag: a signal, not a contract. The field does not carry amounts, currencies, or payment mechanics — v0.1 deliberately defines no negotiation or payment protocol. What it carries is intent, in a vocabulary an agent can act on: proceed without a commercial conversation (free), expect one about an existing paid offering (paid-tier), or start one before doing anything (contact). The details live where the spec points them: with the owner, reachable through the owner.contact in the file's header. How to charge agents for access builds the fuller playbook on top of this field.
The three values, as an agent reads them
free is a complete answer: operate on the rule's other terms — its actions, rate limit, data-use terms — with no commercial step. The blog sample's default and the store sample's reading rule both use it. paid-tier is a signpost: the owner has a paid tier for this kind of access, and the agent (in practice, its operator) should expect the relationship to run through it; the store sample attaches it to its 60-requests-per-minute shopping rule, pairing the fastest pace with the paid terms. contact is the commercial twin of the conditional verdict: no terms exist yet for you, so begin by talking. Note the fields are independent — a rule can be allowed: yes with paid-tier terms, or conditional with free terms once contact is made.
Mixing terms across rules
Because terms are per rule, a policy can price attention differently by agent and by job. A publisher might offer every agent read and quote free, attach paid-tier to crawl-full-site for anyone, and set contact on the catch-all. A store might invert it: shopping assistance free because it brings customers, bulk catalogue access paid because it arms competitors. The format takes no position; it only requires that each rule carry one of the three values, so no agent has to guess whether a commercial conversation stands between it and the work. When the same agent should face different terms for different jobs, remember the constraint from per-agent rules: one rule per identifier, so the terms in that single rule must carry the whole relationship — choose the value that describes the headline bargain.
What paid-tier does not do
It does not collect money, meter usage, issue keys, or verify payment — v0.1 has no machinery for any of that, and the spec lists real-time negotiation among its deliberate omissions. Declaring paid-tier with no actual tier behind it is the one genuinely bad use of the field: an operator who follows the signpost and finds no tier, no prices, and no reply has learned your file overpromises. Publish the value when a real offering exists — even a simple "email us for the data tier sheet" counts, if a human answers — and use contact while it does not.
Expect the terms you publish to be quoted back to you — in partnership emails, in procurement documents, occasionally in disputes about what an agent was entitled to do. That quotability is the field working as intended, and it argues for a small editorial discipline: before publishing, read each rule's commercial value aloud next to its verdict and its action lists, and confirm the three tell one story a stranger would summarise the way you would. yes with paid-tier and a crawl refusal says "work here, pay for the privilege, do not mirror us" — coherent. conditional with free and no rate limit says something murkier. Terms are the shortest sentences in your file; make them the clearest.
Worked example: a photography archive prices its catalogue
Fictional example. The Delgado Archive, a fictional stock photography library with 62,000 images, splits its terms three ways across 4 rules. Reading agents get read and quote on free terms — captions and metadata are its shop window. One named agent gets download of preview images on paid-tier terms at 20 requests per minute, feeding a licensing desk that invoices monthly. crawl-full-site is disallowed for every named rule and the catch-all is conditional with contact terms, so bulk interest starts as an email, not a scrape. In the first half-year, the archive signed 3 paid preview agreements that began as policy reads — the file did not negotiate them, but it told the right agents exactly where the till was.
Setting commercial terms in five steps
- Decide what is genuinely free. Mark the access you give away gladly as
free— usually reading and quoting. - Point paid-tier at a real tier. Publish
paid-tieronly where an offering and a respondent exist. - Use contact as the honest placeholder. Where terms depend on who is asking, say so with
contact. - Price per rule. Set terms rule by rule; let different agents and jobs carry different bargains.
- Keep the contact alive. Every value except
freeroutes toowner.contact— make sure it is staffed.
Keep reading
data_use_terms Explained: Retention, Resale, and Training · Agent Identifiers Explained: the vendor/agent Format · Agent Policy vs robots.txt, Compared · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
Does paid-tier state a price?
No. The field is a three-value signal, not a price list. Amounts, currencies, and payment mechanics are deliberately outside v0.1; the paid-tier value tells the agent a paid offering exists and points it to the owner contact for details.
Can one policy mix free and paid-tier rules?
Yes — that is normal use. The store sample gives its reading agent free terms and its shopping agent paid-tier terms in the same file. Terms attach to rules, and rules attach to agents, so each relationship carries its own bargain.
What is the difference between contact terms and a conditional verdict?
They govern different things. allowed: conditional pauses the agent until the owner has been contacted — a question of permission. commercial_terms: contact says the commercial basis must be negotiated — a question of price. A rule can carry either, both, or neither.
What if I charge nothing but want attribution?
Set commercial_terms to free and put the attribution requirement in data_use_terms, as the blog sample does: its terms welcome agents that attribute and link back. Data-use terms are the plain-language field for non-price conditions on how your content is used.
Do commercial terms make the policy a contract?
The spec is explicit that a policy is the owner's unilateral declaration, not legal advice, and a validator's valid verdict is schema conformance, not a legal opinion. The terms state your offer in standard form; whatever legal weight they carry comes from law outside the format, not from the file.
Generate a policy — free · Validate a policy · What an agent access policy is