Identify consented website visitors with MCP

AgentPixel provides a consent-led tracking pixel and account-scoped contact retrieval. Identity resolution depends on current consent, eligibility and available matches. It does not guarantee identifying every visitor.

1. Connect your agent

Open Connect AgentPixel. The public connection exposes signup and discovery. Use your own confirmed account key for pixel and contact tools.

2. Start your account

Ask your agent to run signup_free(email, display_name) with your own details. Keep its account_id and private signup_token. Read the 6-digit code in the AgentPixel email to your agent. It calls confirm_signup(account_id, code, signup_token), which returns your private key once. The code and the signup token both last 24 hours; resend_code(email) sends a new code. Save it in your client's secret storage. It belongs in a private connection header, never in a tool argument or public repository.

3. Prepare your site

Use whoami(), setup_status() and list_pixels() to check your account and existing tags first. Reuse the pixel for the exact domain when it already exists. Use create_pixel(domain) only when you need a tag for a site you control. Choose the actual business identity, privacy-policy URL and purposes with configure_consent(pixel_id, ...). Include the resolution purpose only where appropriate for your site and visitors. Review the returned notice with get_policy(pixel_id). Install the returned consent-aware snippet on that site. check_install(pixel_id) checks and saves installation status; a generated snippet alone is not a verified install.

4. Review consented results

Use get_contacts(pixel_id, after=0) to start at the first stored contact. After successfully processing the entire returned batch, commit high_water as the next after. If processing is interrupted, retry from the last committed cursor and deduplicate by the returned stored contact id. No rows means no stored results for this scope. It is not proof that a visitor was identified. Visitors who decline identification are not resolved. Honor withdrawals and the applicable site policy.

Pricing and recovery

30-day trial without a card, then $1 per account/month. Includes 3 pixels and 500 new contacts per UTC calendar month. No extra charges. New resolution pauses when the trial expires until subscribed. At the monthly contact limit, new resolution pauses until the next UTC calendar month; subscribing does not raise this limit.

If the account is paused, use whoami() and setup_status() to find the next action. Fix invalid arguments rather than repeating signup. For a temporary provider error, retry with bounded backoff. Do not send real signup email in an automated test.