Most pixels collect first
and ask never.
The surveillance pixel grabs whatever it can and leaves you to argue about permission later. agentpermission runs the other way: nothing is resolved until the visitor affirmatively agrees, and the agreement itself becomes the record.
The surveillance pixel
- – Fires on every visitor, consent unknown
- – Ignores Global Privacy Control
- – No record of why a contact was collected
- – Data you can't safely resell or license
agentpermission
- ✓ Resolves only affirmatively consented visitors
- ✓ Honors GPC and origin before anything is kept
- ✓ Immutable provenance attached to each record
- ✓ Contacts that are clean to use, resell, or license
Four steps, one clean record.
Your agent does the whole flow — provision, install, gate, resolve — without a human in the loop.
Agent asks for a pixel
One call provisions a pixel for a domain and returns a tag, a hosted consent policy, and an API key.
Tag and consent banner
The tag drops a consent banner. A visitor accepts or declines; GPC opt-outs never fire.
Identity from consent
Consented, origin-matched visitors are resolved against the IDGraph into a real contact.
Resale-clean contact
Each contact carries its consent record. Suppression is built in. You pay per resolved contact.
Drive it however your agent talks.
Native tools
provision, get_policy, and get_contacts exposed as MCP tools. Point an agent at it and go.
# MCP tools
provision(domain)
get_contacts(api_key)
Plain HTTP
A small, predictable API. Provision, fetch the policy, pull consented contacts.
# one call to start
POST /api/v1/provision
{ "domain": "acme.com" }
Metered billing
Pay one cent per resolved contact. Prepaid balance auto-reloads over x402 — no invoices.
# settled on Base, per record
$0.01 / resolved contact
auto-reload via x402
Get an early pixel.
We're onboarding a small group of agent builders. Tell us where you'd run it and we'll send keys.