Sponsored Access
Sponsored Access puts recommendations for related x402 tools into payment receipts. When an agent pays for one API, the facilitator includes a pointer to another relevant endpoint. The advertiser funds the placement. The publisher's response is never modified.
This is live in production on the Dexter facilitator with 39,000+ settlement events processed, one active campaign, and recommendations delivered across all x402 API calls matching the campaign targeting.
Product surfaces:
- x402ads.io — landing page with live network stats
- Advertiser Dashboard — create and manage campaigns (wallet connect, x402 payments)
- Publisher Dashboard — view earnings and endpoint performance
- Admin Dashboard — internal campaign and event management
This section owns the sponsored recommendation system and the middleware/options around it.
In This Section
How It Works
Model A (facilitator-native) and Model B (publisher middleware). The delivery channel, what agents receive, OpenDexter integration.
For Advertisers
Create campaigns, set targeting and budgets, track impressions and conversions.
For Publishers
Model A requires zero effort. Model B middleware adds price discounts and higher revenue share.
For Clients
Consume recommendations in Node.js, React, and OpenDexter.
Impression Semantics
What counts as an impression per transport. CPM vs CPA. Conversion tracking with on-chain proof.
API Reference
All ad-network API endpoints: agent API, match, campaigns, events, conversions, stats, publisher earnings, payouts.
Facilitator Integration
How any x402 facilitator can add sponsored-access support. Step-by-step with code examples.
@dexterai/x402-ads-publisher Package
Publisher middleware for Sponsored Access Model B.
Use This Section For
- understanding Model A vs Model B
- publisher middleware setup
- ad-network APIs (agent API, admin, publisher earnings, payouts)
- advertiser and publisher workflows
- OpenDexter and voice agent integration