RINGSIDE · DEVELOPER ACCOUNTS

Your customers get their own account, created by your code.

You build things for other people. Agency work, an internal platform, a product with AI bolted into it. The awkward part has always been the account: either everyone shares your key and your bill, or every client goes through a signup you have to talk them through, twice, on a call.

A developer key removes that step. You POST an email and a username, and a full Ringside account exists on the other side with its own login, its own vault and its own key. You decide who pays for it at creation time, in the same call. Nobody clicks anything and nobody waits for a human.

Auto-approved · one rsk_ key · up to 10 live accounts · four funding modes

What enrolling actually gives you

One key does the provisioning

Turn on developer features from your profile, accept the Developer Addendum, and you get a single rsk_ key. It authenticates POST /v1/accounts and nothing else. It is not a tenant key and it cannot spend. Rotate it whenever you want.

Ten accounts, each a real one

Every account you create has its own login, its own vault, its own ko_ key, and can call Brains from day one. Not a sub-entity on your bill. Close one and the slot comes back. Past ten, open a ticket.

You hold the mini-admin view

Balance and spend for every account you provisioned, in your own Ringside dashboard, plus the ability to close them. Funding only ever moves in one direction, from your wallet to theirs.

Who pays, decided at creation

The funding mode is one field on the create call and it settles the commercial relationship for that account. Money only ever moves from you to your customer, every transfer is atomic and checked against your balance, and nothing is reversible by the account itself. On linked accounts there is no platform spend cap, so capping a customer's burn is a control you set, not one you inherit.

funding: "self"

Self-funded

Create the account dry. Your customer signs in and puts their own card or voucher against it. You carry none of the spend and none of the collections.

funding: "grant"

Grant

Pass amount_usd and we debit your wallet and credit theirs inside the same call. One round trip and the account is usable. Good for trials, credits and anything you promised in a sales call.

funding: "voucher"

Voucher

Mint a wallet-backed voucher up front, which debits you at mint time, then hand the code in at creation. Useful when the money is committed before you know who the account is for.

funding: "linked"

Linked wallet

The account never holds money at all. Every call it makes lands on your wallet, so you carry the usage and bill your customer however you already bill them. Ringside stays out of that arrangement entirely.

One call per customer

Authenticate with your rsk_ key. A 201 comes back holding the account, its own ko_ key shown exactly once, the opening balance, and an onboarding message written to be pasted straight into whatever you send your customer.

curl https://api.fightclub.pro/v1/accounts \
  -H "Authorization: Bearer $RSK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "dev@customer.com",
    "username": "customer_acme",
    "password": "a-strong-password",
    "funding": "grant",
    "amount_usd": 25.0
  }'

Ready when you are

Enrolment is auto-approved and the Addendum is a two-minute read. The first account you provision can be a real one.