Create and review rules without blocking any request.
MACHINE ACCESS RULES
Set clear rules for AI traffic.
Choose which AI traffic to allow, observe, or block. Start by seeing what your rules would match, simulate them against recent traffic, and enable blocking only when your site is ready to apply the decisions.
Enter the connection ID and management key for the site you want to manage.
Test the rules against recent AI traffic. Nothing is blocked during simulation.
Blocking takes effect only when enforcement is enabled and your site integration is connected to apply the decision.
Run a simulation before considering enforcement.
Use this one-time decision key only in the site integration that applies your access rules. It cannot edit your policy or manage the connection.
Evidence and enforcement boundaryRules can use the observed provider, agent, request purpose, HTTP method, path, and identity-confidence level. User-agent names can be spoofed, so stronger identity evidence should be required for sensitive rules. AIWebSignals does not see private prompts, model reasoning, or hidden user intent.
Add paid access when it makes sense
Agent Policy decides who can access a resource. AI Revenue can add an x402 payment requirement for licensed machine access. Keeping access rules and payment settlement separate makes it clear whether a request was blocked, priced, or actually paid.
Configure AI Revenue · Return to AI ImpactWHY THIS LAYER EXISTS
A human pageview and a machine request are not the same event.
The difference runs from data and protocols through identity, permission, intent, and value. The foundational explainer shows where AIWebSignals fits in that stack.