# Evaluate AgentPixel safely

Evaluation uses a permanently isolated account, not a production customer account. It cannot send email, issue another key, subscribe, call the live pixel provider, read customer contacts, or run IDGraph resolution. Samples are clearly labeled synthetic and are kept in a separate table.

## 1. Connect privately

Ask the account owner for the private evaluator profile or the registry's private test profile. Credentials are never shown on this public page. Connect to `https://agentpixel.io/mcp` with `Authorization: Bearer <private evaluator key>` or `X-API-Key: <private evaluator key>`. Do not pass the key as a tool argument or publish it.

Call `whoami`. Confirm `evaluation_mode` is true and `data_kind` is `synthetic`. Check `evaluation_expires_at`. The profile ends at its original 30-day trial boundary; it does not renew or charge automatically. The owner can revoke the key at any time. Ask the owner for a renewed private profile when access needs attention; expiration or missing scope never changes this account into a production account.

## 2. Review the controlled site

The only allowed hostname is `staging.allsourcedata.io`. The controlled page is [AgentPixel evaluation page](https://staging.allsourcedata.io/evaluation-test/). `create_pixel` returns an `eval_` pixel ID and consent tag. Repeating the same domain returns that account's existing evaluation pixel. `check_install` fetches only this exact page and rejects redirects, including redirects within the same host. It does not inspect the staging homepage.

The owner installs the tag on this controlled page. Configure consent, then use the page to accept identification. GPC, decline, and withdrawal prevent tag activation for that visitor. Reading the account's synthetic examples requires at least one saved, current acceptance of resolution consent. It does not infer consent from a browser cookie. A checked installation is only Done for the tag installation, not identity resolution.

## 3. Read the examples

Example agent request: List my pixels, then get_contacts for my eval_ pixel with after set to 0. Tell me which fields show that these are synthetic examples and whether consent is saved.

Use exactly one of `on` (UTC date YYYY-MM-DD) or `after` (nonnegative contact cursor). Use returned `high_water` as the next cursor. Before accepted current resolution consent, contacts are empty and `next_action` tells you to accept consent on the controlled page. After consent, two static synthetic example records are available. Their addresses end in `example.invalid`; they are not identified visitors. Withdrawal hides the examples again. The tag does not contact live identity or advertising providers.

## Limits and readiness

The normal public terms remain a 30-day no-card trial, then $1 per account/month, 3 pixels and 500 new contacts per UTC calendar month, with no overage charges. This evaluator cannot pay or switch to live processing. It contains two synthetic fixture records and is bounded by the original trial end. No customer data or live resolution is evidence from this evaluation. A real IDGraph outcome and real payment settlement require separate authorized tests.

For 400 errors, correct arguments. For 401, check the private connection key. For 403, follow the scope or expiry message and contact the owner. For 404, use your own pixel ID. For 409, ask the owner about domain registration. For 429, wait. For 502/503, retry with bounded backoff. Do not retry signup or key issuance blindly; evaluator connections cannot use those tools.