You write an ordinary HTTP endpoint and host it yourself. We route paid calls to it, sign every one so you can prove it came from us, meter the developer’s spend, and settle your earnings into a double-entry ledger.
New here? Start with the quickstart, or go straight to thereference endpoint — one file, compiled and tested in our CI, with the whole contract handled.
Everything in these docs#
Start here
- OverviewWhat you build, what we do, and who holds what.
- QuickstartHandle, endpoint, publish, paid. Five steps.
- Reference endpointA complete server you can clone. Compiled and tested in our CI.
The contract
- Verifying a requestThe creator key, the six-field signature, and why both exist.
- Endpoint requirementsHTTPS, timeouts, size caps, streaming, and what we refuse.
- Versions are immutableWhy a published price can never change, and how to ship v2.
Getting paid
- When you earnThe 10% fee, when a call settles, and when it does not.
- PayoutsStripe Connect, the $5 minimum, and the gate that is still shut.
- When calls do not arriveReading your endpoint health, and what de-listing means.
Who holds what#
| Thing | Who holds it |
|---|---|
| Your tool’s code and infrastructure | You |
| Your bank details | Stripe. We hold a reference and capability flags, never the account itself |
| The creator key | You, after it is shown once. We keep only a derived value |
| The signing private key | Us. You only ever need the public half |
| Request and response payloads | Nobody. They transit and are never stored |
| Your earnings record | An append-only double-entry ledger. A correction is a new row, never an edit |