---
title: Monetization (Renamed → Partner Program)
description: AI Gateway monetization has been renamed and restructured as the Partner Program
---
# AI Gateway monetization → Partner Program
AI Gateway monetization has been **renamed and restructured** as the **[Partner Program](/docs/partner-program)**. **Existing integrations using the old `X-Merchant-*` headers continue to work without code changes** — see the backwards compatibility table below.
## What changed
The previous "monetization" feature on the AI Gateway — adding a percentage markup to AI calls and earning the difference — is now the **Partner Program**, with a clean affiliate / revenue-share legal model.
| Old | New | Backwards compatible? |
|---|---|---|
| `X-Merchant-Id` header | `X-Partner-Id` (canonical) — `X-Merchant-Id` is now a legacy alias | ✅ Yes |
| `X-Merchant-Wallet` (per request) | Accepted but ignored — payout is on the Partner record | ✅ Yes (no-op) |
| `X-Merchant-Fee-Percent` (per request) | Accepted but ignored — pricing tier is on the Partner record | ✅ Yes (no-op) |
| Per-request fee % | Fixed tier set at onboarding (0/5/10/15/20%, default 10%) | Existing partners migrated individually |
| Per-call on-chain settlement to merchant wallet | Monthly partner commission paid by Agnic from its own AP | Partners receive notification of new payout schedule |
## Do I need to migrate?
**No.** Existing integrations using `X-Merchant-Id` continue to work. You do not need to change your code. If you want to use the new canonical header name `X-Partner-Id`, you can — both names point to the same partner record.
The old `X-Merchant-Wallet` and `X-Merchant-Fee-Percent` headers are still accepted (so your code does not error if you continue to send them) but they no longer affect behaviour — the new model uses the Partner record for both payout destination and pricing tier.
## Where to go
Full Partner Program docs with code examples
View commission accruals and confirm your tier