Advertiser control plane

Turn an objective into an authorized campaign.

Set the product, contextual rules, creative and budget. The campaign becomes eligible for placement only after the advertiser signs its exact revision.

CampaignManifestV2

Create an advertiser-authorized campaign

Campaign data is written to PostgreSQL. Launch requires this wallet's EIP-712 signature.

The agent proposes editable fields. Your wallet signature is still required to launch.

Advanced targeting and creative
Eligible topics
Eligible intents

Advertiser approval

Privy payer configuration is unavailable; browser-wallet settlement remains reviewable.

No draft selected

Create a campaign with your own product, rules, budget, and creative.

Persisted campaigns

No campaigns have been stored.

Open the V1 commitment utility

Local result

No commitment yet

Complete the campaign details to create deterministic V1 hashes in this browser. Nothing is signed, uploaded, or broadcast.

Privy policy

Default deny, two bounded actions

A configured server wallet can approve only the bounded amount and call the exact settlement function allowed by its provider policy.

Disallowed signing request
Denied by defaultRequests must match the configured policy
Bounded settlement
Amount and recipient boundedVerified settlements appear in the live ledger
1Prepare

Hash campaign, placement, product, and exact content.

2Authorize

Evaluate private targeting and max bid in CRE_SIMULATED.

3Settle

Privy pays test USDC directly to the signed recipient.

4Verify

Graph and RPC must agree before the paid label appears.

Campaign signed. Next: match a live context

Ask a relevant question, pass the safety and relevance gates, authorize the exact placement ticket, then settle and verify its receipt.