Referrer
Integrate.
Three accepted ways to be attributed as the referrer on a paid call. Pick whichever fits your stack, all three earn the same commission.
Mode 1
Referrer key
Simplest. Best for skills, MCP servers, and any caller that can't sign per request.
Create a key on the referrer keys page (bind it to your payout wallet at creation time). Send it on every request via the
X-Chest-Referrer-Key header:curl -H "X-Chest-Referrer-Key: cg_pub_live_..." \ https://gate.chest.sh/g/<slug>/<path>
Mode 2
Signed wallet header
Highest trust. Best for clients that already hold an ed25519 keypair.
Sign each request with your wallet (canonical message:
chest-referrer:{slug}:{amount}). The signReferrer helper in the proxy package handles the message format.X-Referrer-Wallet: <YOUR_WALLET> X-Referrer-Sig: <base64 ed25519 sig> X-Referrer-Payout: <optional: cold wallet>
Mode 3
Unsigned header
Zero setup. Default-on for new gates; merchants can opt out.
For merchants that accept unsigned attribution. Lowest trust, no proof the wallet authorized the attribution, so merchants can refuse. Useful for quick prototypes on a merchant you control.
X-Referrer-Wallet: <YOUR_WALLET>