What's live

An honest line between what runs in production, what we do by hand, and what is still planned.

The programme is young. Rather than describe it as a finished product, here is the line.

Running in production

Partner dashboard: metrics, customers, referral codes and attributions, your nodes, domains, blog, marketing kit, prices, payouts, API keys, webhooks.
Partner API: GET /me, create / read / suspend / restore customers, metrics, prices, payouts — see the API section.
Self-serve API keys: issue and revoke your own, with a scope picker. Killing a leaked key no longer waits on an operator.
Per-key rate limits: 300/min by default, 429 with Retry-After, scoped to the key rather than the partner.
Webhooks: five events, HMAC signature, eight attempts on a widening interval, auto-disable for a broken endpoint, a delivery log and a test button.
Domains with DNS verification and runtime storefront branding by domain.
Price floor: you set your prices; the API refuses anything below the agreed minimum.
Mobile client branding: accent and name arrive per account after sign-in; the logo ships inside a branded build.
Your own nodes: one-shot token, install on your VPS, visible to your customers only.
Trial grants through the API: N days of a plan for a customer, bounded per grant and per calendar month.
A Telegram bot template: a working skeleton in examples/partner-bot — sign-up, trial, account card, Dockerfile.
Payout computation: on the 1st for the previous calendar month, one row per currency, with the rate frozen into the row so it is never rewritten retroactively.
Chargeback gate: a warning, then an automatic suspension when the refund share runs high.

Done by hand (works, but not self-serve)

Sending USDT — the computation is automatic, the transfer is made by an operator who records the hash.
Branded Android/iOS builds — we build them under your bundle id.
The revshare rate — revisited by agreement as volume grows; there is no automatic tier progression.
Raising a key's rate limit — on request, if the default 300/min is not enough for your integration.

Planned, and absent today

Automatic on-chain payout sending (the transfer is manual today).
Selling a subscription through the partner API — payment only goes through the storefront checkout.
Metrics broken down by plan, and churn.

If something on the planned list is critical to your launch, say so on the call — priorities are negotiable.