For Advertisers

An advertiser is an x402 resource operator who wants their endpoint discovered by agents. You create a campaign that targets related API URLs. When agents pay for those APIs through the Dexter facilitator, your endpoint is recommended in the settlement receipt.

Creating a Campaign

1. Register as an Advertiser

Provide your name, wallet address, and network:

POST /v1/advertisers
{
  "name": "Your Project",
  "wallet_address": "YourSolanaWalletAddress",
  "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"
}

2. Create a Campaign

POST /v1/campaigns
{
  "advertiser_id": "your-advertiser-uuid",
  "name": "Promote My Data Tool",
  "budget_total": "10000000",
  "budget_daily": "1000000",
  "max_bid_amount": "1000",
  "target_url_patterns": ["*jupiter*", "*swap*"],
  "target_networks": ["solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"],
  "schedule_start": "2026-03-05T00:00:00Z",
  "rec_resource_url": "https://your-api.com/v1/data",
  "rec_description": "Real-time data feed, 0.001 USDC per call",
  "rec_sponsor_name": "YourProject"
}

All amounts are in atomic USDC (6 decimals). 1000000 = 1.00 USDC. The admin dashboard at /admin/ads accepts human-friendly USDC amounts.

3. Activate

POST /v1/campaigns/{id}/activate

The campaign immediately starts matching against incoming settlements.

Targeting

Campaigns target by URL pattern. The pattern is matched against the resource URL of each settlement:

You can also filter by network (Solana mainnet, Base, etc.) and transport (HTTP, MCP, A2A).

Budget and Bidding

• Budget Total: Maximum lifetime spend for the campaign
• Budget Daily: Maximum spend per day
• Max Bid Amount: Cost per campaign match (deducted from budget on each match)

When the budget is exhausted, the campaign stops matching automatically.

Conversion Tracking

The primary metric for agent-facing recommendations is conversions, not impressions.

A conversion occurs when an agent that received your recommendation subsequently calls your endpoint through the same facilitator. The system records both transaction hashes: the original settlement (where the recommendation was shown) and the conversion settlement (where the agent called your endpoint).

Both hashes are on-chain, publicly verifiable proof that the conversion happened.

View conversions in the admin dashboard at /admin/ads/campaigns/{id} or via:

GET /v1/campaigns/{id}/conversions

Pricing Models

For agent transports, you only pay when the agent actually calls your endpoint. For HTTP, you pay per verified impression (confirmed by beacon).