The key is the business
No field to set, and therefore no field to forge.
Your own site, bot or agent can ask for an exact amount and get back a URL that takes it.
Keys are minted under Developer, and shown once.
A call, end to end
The blast radius
No route and no body carries a venture id. A leaked key touches one business: its own.
No field to set, and therefore no field to forge.
It creates links and takes them down. No endpoint pays anything out.
No transactions, no receipts, no totals. It cannot say what you earned.
No names, no email addresses, no ages, no guardian record.
The surface
| Path | Method | What it does |
|---|---|---|
| /api/fuime/v1/me | GET | Whose key it is, and whether it can sell |
| /api/fuime/v1/payment_links | GET | The live links this key made |
| /api/fuime/v1/payment_links | POST | Make one, $1 to $10,000, USD |
| /api/fuime/v1/payment_links/:id | DELETE | Take down one it made |
A key only sees and deletes the links it made. A misplaced decimal is refused, not clamped. A deleted link stops taking money and the record survives.
The limits
Keys cost nothing and are not a plan feature.
Prefixed like Stripe's and GitHub's, so a secret scanner can match it.
fuime_sk_
Not a resource limit. Three integrations is more than most have.
10
Stops a retry loop filling your dashboard overnight. Take some down and make more.
250
Per key, across all three endpoints.
120
What is missing
Finding that out from a page is cheaper than finding it out from a build.
Every key is live. Make a link for a dollar, then delete it.
Nothing to install, in any language. JSON over HTTPS, and whatever handles that.
Nothing tells your code when a link is paid. You poll the list, or watch the ledger.
No OpenAPI document to generate a client from. This page is the documentation.