Resolution pixel for AI agents

Turn consented
visitors into
contacts.

agentpixel is the pixel your agent provisions in one call. It fires only on a consented visitor, resolves them against a 343M-profile identity graph, and hands back a real contact — with the consent receipt stapled to it.

free first 1,000· $10 / 1,000 after· consent-gated, always
agent → agentpixel
# one call provisions the pixel
POST /api/v1/provision
  { "domain": "acme.com" }

# agentpixel auto-provisions the
# required agentpermission consent tag
→ pixel_id   px_9b4d…ae0b
→ consent_tag px_cd63…3222  ($1/site/mo)
→ tag        <script src="…/px_9b4d.js">

# visitor consents → resolves → billed
contact  { email, name, city, state,
           resale_eligible: true }
How it works

Consent first, contact second.

agentpixel never resolves a visitor it isn't allowed to. Permission is checked against agentpermission on every fire.

01 / PROVISION

One call

Your agent provisions a pixel for a domain. The required consent tag is set up automatically.

02 / GATE

Permission check

On every fire, agentpixel asks agentpermission whether this visitor consented. No record, no resolve.

03 / RESOLVE

Identity graph

Permitted visitors are resolved into a real contact — email, name, location.

04 / COLLECT

With provenance

Each contact carries its consent receipt. Pull them by API; pay per cartridge.

Agent-native

An endpoint, not a signup.

agentpixel is provisioned and paid for by agents, over plain HTTP. One call sets up the pixel and its required consent tag; pricing is machine-readable and payment is HTTP-native, so an autonomous agent can resolve and settle with no human in the loop.

01 / PROVISION

One authenticated call

Your agent provisions a pixel for a domain with a single POST — the agentpermission consent tag is set up in the same call.

02 / PAY

x402, the native way

HTTP 402 used as intended. The agent signs a USDC payment from its own wallet to buy a contact cartridge — no card, no account.

03 / DISCOVER

Self-describing price

GET /api/v1/pricing returns the free tier, cartridge price, and x402 challenge inline, so an agent can read the terms and pay on its own.

# 1 - agent buys a cartridge, no payment yet
POST /api/v1/provision  { "domain": "acme.com" }
-> 402 Payment Required
   PAYMENT-REQUIRED: { asset: USDC / Base,
                      amount: 10.00 / 1,000 contacts }

# 2 - agent signs a USDC payment, retries
POST /api/v1/provision
   PAYMENT-SIGNATURE: <signed authorization>
-> 200 OK
   PAYMENT-RESPONSE: { settled: true, tx: 0x... }
   { pixel_id: px_..., consent_tag: px_... }
Pricing

Free to start. Cartridges after.

Free tier

First 1,000 contacts

$0

Every new pixel resolves its first 1,000 consented contacts free. No card, no wallet, no signup.

Cartridges

1,000-contact blocks

$10 / 1,000

After the free tier, each 1,000-contact cartridge is $10, settled over x402. Auto-reloads as you resolve.

agentpermission is required. Every agentpixel pixel runs on an agentpermission consent tag ($1 / site / month), provisioned automatically when you create the pixel. A visitor is only ever resolved after they affirmatively consent and aren't GPC-opted-out — that permission record is what makes the contact clean to use.