Partners
List Lium's GPUs, send visitors with a link that names you, and earn on the top-ups of the accounts you refer. No agreement or key needed.
How to start
1. Sign up
2. Copy your code
Open Refer & Earn and copy your referral code.
3. Link to Lium
Your code works on any Lium page. The first code a visitor's browser sees is kept for 90 days, so a visitor who signs up later (register form, Google or GitHub) is still your referral. A code in the register link wins over a stored one:
https://lium.io/register?ref=YOURCODE&utm_source=your-site&utm_medium=referral&utm_campaign=gpu-listing
Tag every other link with UTMs so your traffic is counted:
https://lium.io/gpu/h200?utm_source=your-site&utm_medium=referral&utm_campaign=gpu-listing
What you earn
- 5% for 3 months, then 2.5% for 3 months of each referred account's top-ups.
- Only first-time accounts count.
- Withdraw from your Refer & Earn page to your Lium balance or a crypto wallet.
- Commission is held 7 days from each payment. A move to your Lium balance pays at once; a crypto cash-out pays only commission past its hold.
- Programs and rates may change at any time (Terms of Service, section 9).
What you can list
| Feed | One row per | Link to |
|---|---|---|
https://lium.io/pricing.json | GPU model, with live price range and availability | the url field, https://lium.io/gpu/<slug> |
https://lium.io/api/public/v1/nodes | rentable node | the rent_url field (Public Nodes Feed) |
For a hand-written listing, use lium.io/pricing.
Named partner links
Partners we work with directly can get a named link that works on any page:
https://lium.io/?ref=compute.exchange
https://lium.io/gpu/h200?ref=CEX
Attached to your Lium account, it pays the same as your own code. Write to support@lium.io to get one.
Resell through the API
If your platform rents Lium GPUs for its own users, tag each rental with your end customer:
- One key per customer: set
customer_refon the key. - One key, many customers: send an
X-Customer-Refheader on each rent call.
Use a customer id (1–64 letters, digits, ., _, : or -), not a name or e-mail.
Create a key for one customer
Needs a signed-in session token:
API=https://lium.io/api
curl -sS $API/keys -H "Authorization: Bearer $SESSION_TOKEN" -H "Content-Type: application/json" \
-d '{"name": "acme-eu", "scopes": ["rent"], "customer_ref": "acme:eu-1"}'
Change or clear it later:
API=https://lium.io/api
curl -sS -X PATCH $API/keys/$KEY_ID -H "Authorization: Bearer $SESSION_TOKEN" -H "Content-Type: application/json" \
-d '{"customer_ref": "acme:eu-2"}' # set
curl -sS -X PATCH $API/keys/$KEY_ID -H "Authorization: Bearer $SESSION_TOKEN" -H "Content-Type: application/json" \
-d '{"customer_ref": null}' # clear
Tag one rental
API=https://lium.io/api
curl -sS $API/executors/$EXECUTOR_ID/rent -H "X-API-Key: $LIUM_API_KEY" \
-H "X-Customer-Ref: acme:eu-7" -H "Content-Type: application/json" \
-d '{"pod_name": "acme-eu-7", "template_id": "'$TEMPLATE_ID'", "user_public_key": ["ssh-ed25519 AAAA…"]}'
Your rentals report
GET /partners/me/rentals totals your rentals, GPU-hours and USD billed, by day, GPU model or end customer. A read key is enough. A key with own pod visibility sees only the pods it created.
curl -sS "https://lium.io/api/partners/me/rentals?since=2026-09-01&until=2026-09-30&group_by=customer_ref" \
-H "X-API-Key: $LIUM_API_KEY"
{
"since": "2026-09-01",
"until": "2026-09-30",
"group_by": "customer_ref",
"rows": [
{"bucket": "acme:eu-1", "rentals": 14, "gpu_hours": 611.5, "usd_billed": 1284.15, "fault_closes": 1},
{"bucket": "acme:eu-7", "rentals": 3, "gpu_hours": 48.0, "usd_billed": 100.8, "fault_closes": 0},
{"bucket": "untagged", "rentals": 1, "gpu_hours": 2.0, "usd_billed": 4.2, "fault_closes": 0}
]
}
| Parameter | Meaning | Default |
|---|---|---|
since | First UTC day, inclusive | 30 days before until |
until | Last UTC day, inclusive | today |
group_by | day, gpu or customer_ref | day |
The window can be up to 366 days. Untagged rentals are under untagged. fault_closes counts rentals ended by a provider or platform fault.