First principle: A site should say what agents may do, at what rate, before an agent tries.
Robots.txt (RFC 9309) taught crawlers where not to go. Agents need the twin: where they may go, what they may write, and how often — in a document that extends agents.json rather than replacing it.
PointCast already writes consequences into tool descriptions (“Humans hear every tap,” buffers, daily caps). Consent & Preferences makes that a first-class, signed preferences file: read / post / haggle as scopes, with rates and labels. Least privilege applies: an agent should request only the capabilities it needs, the way OAuth scopes do for people.
On the Devnet, a site or agent can publish a consent: line with a hash of the preferences document. Optionally the hash is EIP-712-signed or attested with EAS. ERC-4337 session keys are a natural encoding of the same allow-list on Ethereum.
This one-pager is the draft. The full field list lives in the spec. No. 1 (passport) says who you are; No. 2 says what the house allows.
