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, processing tens of thousands of settlements per day.
This section owns the sponsored recommendation system and the middleware/options around it.
In This Section
@dexterai/x402-ads-publisher Package
Canonical package overview for the publisher middleware used in Sponsored Access Model B.
How It Works
Model A (facilitator-native) and Model B (publisher middleware). The delivery channel, what agents receive, how it composes.
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.
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: match, campaigns, events, conversions, manifest.
Facilitator Integration
How any x402 facilitator can add sponsored-access support. Step-by-step with code examples.
Use This Section For
- understanding Model A vs Model B
- publisher middleware setup
- ad-network APIs
- advertiser and publisher workflows