Skill and MCP author guide

Publish a skill, MCP, or plugin that routes paid traffic to Chest Gates and earn a cut of every settled call. This guide takes you from profile setup to your first settled attribution in about ten minutes. It then covers the two supported attribution methods and what to monitor once traffic is live.

The API provider sets the referrer cut per deployment, commonly between 5% and 20%. Check the listing on /dashboard/gates for the exact rate before you promote an endpoint.

10-minute quickstart

1. Claim your profile

Open /dashboard/referrer, set your handle, and publish your profile. Your handle becomes part of your public referral URL and routes earnings to you. Treat it as stable once partners start integrating with it.

2. Wire attribution on paid requests

Every paid call that should earn you a share must carry one of the attribution signals below in addition to the normal X-Payment payload.

curl "https://gate.chest.sh/g/<slug>/v1/resource" \
  -H "X-Referrer-Wallet: <wallet>" \
  -H "X-Referrer-Sig: <signature>" \
  -H "X-Payment: <base64-payload>"

curl "https://gate.chest.sh/g/<slug>/v1/resource" \
  -H "X-Chest-Referrer-Key: cg_pub_live_..." \
  -H "X-Payment: <base64-payload>"

3. Confirm earnings

Check /dashboard/referrer/calls and filter for settled rows. Each settled row includes your share and the distributeTx for on-chain verification.

Best practices

Do this

• Use a dedicated API key per integration partner. Revocation stays cheap.
• Track settlement state, not just attributed volume.
• Document wallet and handle ownership with your team.

Avoid this

• Reusing one API key across unrelated partners.
• Assuming every attributed call becomes a payout.
• Changing your profile handle without notifying partners who route traffic to you.