Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in
  8. 11Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  9. 12Billing
  10. 13Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  11. 14Router
  12. 15Guardrails
  13. 16Knowledge

Reference

  1. 17API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GTasks
    8. HEmbeddings and rerank
    9. IJobs
    10. JUploads
    11. KFiles
    12. LBatches
    13. MWebhooks
    14. NVector stores
    15. ODeployments
    16. PRequirements and headers
    17. QErrors
    18. RUsage
    19. SVersioning
  2. 18Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 19Changelog
Sheet indexProvider setup

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in
  8. 11Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  9. 12Billing
  10. 13Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  11. 14Router
  12. 15Guardrails
  13. 16Knowledge

Reference

  1. 17API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GTasks
    8. HEmbeddings and rerank
    9. IJobs
    10. JUploads
    11. KFiles
    12. LBatches
    13. MWebhooks
    14. NVector stores
    15. ODeployments
    16. PRequirements and headers
    17. QErrors
    18. RUsage
    19. SVersioning
  2. 18Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 19Changelog
13
  1. Docs/
  2. Provider setup/
  3. Earnings
(Detail E)
llms.txt

Earnings and payouts

On this sheet9 sections
  1. Four states, never one total
  2. While a new GPU is checked
  3. Holds on your earnings
  4. Batch work
  5. Work history
  6. Payouts
  7. Earnings as Credits
  8. Settlement Statements and self-billed invoices
  9. Accepting or objecting to an invoice

GPU earnings shows what your devices earned and what is ready for payout, per settlement period and per device, with each GPU of a machine under it. Earnings depend on eligible work being assigned and performed.

Fig. 1, sheet 13Provider setup

Four states, never one total

StateWhat it meansCan be paid out
EstimatedWork completed, being processed. May changeNo
AccruedCounted in this period, settled when the period ends; still subject to verification and any holdNo
PayableSettled amounts you can request as a payoutYes
PaidSent, with the payout referenceNo
  • State
    Estimated
    What it means
    Work completed, being processed. May change
    Can be paid out
    No
  • State
    Accrued
    What it means
    Counted in this period, settled when the period ends; still subject to verification and any hold
    Can be paid out
    No
  • State
    Payable
    What it means
    Settled amounts you can request as a payout
    Can be paid out
    Yes
  • State
    Paid
    What it means
    Sent, with the payout reference
    Can be paid out
    No

Settlement is monthly: a period settles at the month's end and is paid within 14 days. A payout is requested from the payable amount only, never from estimated or accrued.

While a new GPU is checked

What a new GPU earns while HIPS checks it is held until the check passes, and only that GPU's earnings: the rest of your devices are not held. Once the check passes, the held amounts settle as any other.

Holds on your earnings

Standing and holds, on GPU earnings, names each hold on your earnings and says beside it until when, or what it means where it has no end date. Besides a new GPU's check, above:

GPU earnings saysWhat it means
No published rateThis work ran with no published rate. The line is kept in full until HIPS prices it. It has no end date
  • GPU earnings says
    No published rate
    What it means
    This work ran with no published rate. The line is kept in full until HIPS prices it. It has no end date

Batch work

Batch work is one request of a buyer's batch at a time, run when capacity is free within the batch's window. It pays your share of the batch rate, half the on-demand rate of the same model, by the same share rule as every other job. A device is offered batch work only when its share clears the device's minimum price, and a request the batch's window closes on is neither charged nor paid.

Work history

Work history lists every job your devices ran: the time, the device, the model and engine, the kind of work, the outcome (completed, failed, rejected, interrupted, timed_out) and the job id, filtered by device, date range, outcome and kind of work. What a job cut short earns follows the Provider Agreement: a job ended by the device, its app or you earns nothing; one ended by HIPS, or canceled by a buyer after output began, earns the price of the units it produced before it ended; one canceled before output, nothing.

hips-provider history shows what the computer recorded itself, day by day, without earnings.

Payouts

Payouts go by bank transfer to a bank account you connect through Stripe, decided by the one country where you are paid, never by where your machines run. On Payouts, Connect a bank account opens Stripe in a new window, where you enter your bank details; HIPS does not store them. The screen follows Stripe's checks by itself and says what Stripe still needs.

Where you are paidPayout
United States, United Kingdom, the European Economic Area, Switzerland, CanadaBank transfer through Stripe Connect
Japan, Singapore, South Korea, Taiwan and AustraliaBank transfer through Stripe Global Payouts, opening in each country once Stripe confirms it
Every other countryNot available there yet
  • Where you are paid
    United States, United Kingdom, the European Economic Area, Switzerland, Canada
    Payout
    Bank transfer through Stripe Connect
  • Where you are paid
    Japan, Singapore, South Korea, Taiwan and Australia
    Payout
    Bank transfer through Stripe Global Payouts, opening in each country once Stripe confirms it
  • Where you are paid
    Every other country
    Payout
    Not available there yet

Paid work opens in a country once payouts open there; until then a device there takes test work only. No payout is made to a sanctioned country. The terms of the program are on the public Earn page and in the Provider Agreement.

Earnings as Credits

You can take a share of each month's payout as Credits in a workspace you own, instead of money, once HIPS publishes the Additional Terms "Earnings as Credits" and you accept them on Payouts. Until they are published, Payouts says so and every payout goes to your bank account.

  • One dollar of earnings becomes one dollar of Credits, with no bonus. Credits expire 12 months after they are added and never become money again.
  • The share is a whole percent of the month's whole payout, from 0 to 100, taken at the settlement on the 7th; the rest goes to your bank account. A change applies from the next settlement.
  • The payout threshold is judged on the month's whole payout, before the split: below it nothing converts and the month waits, as a payout does; at or above it both parts are paid, the bank part whatever its size.
  • Move to Credits now moves what is settled as payable and not yet paid into Credits at once, at most 10 times in 24 hours.
  • Credits wait for what a payout waits for: your verified identity, your payout profile, the tax information collected with your bank account through Stripe, payouts open in your payout country, and no hold on your account.
  • Credits go only to a workspace you own alone, with no other member or invitation, that is not frozen for a card dispute, and pay off a negative balance there first. Deleting that workspace ends the choice.
  • Stop taking Credits on Payouts at any time: from the next settlement every payout goes to your bank account, and the Credits already added stay. Closing your provider account ends it too.

Settlement Statements and self-billed invoices

For each month in which you had earnings, an adjustment or a netting entry, HIPS gives you a Settlement Statement no later than that month's Payable Date, the 14th day after the month ends. It is written once the month's payouts have run, on the 13th at the latest, and sent to you by email. GPU earnings lists your statements under Statements, newest first; a row opens to the detail, and its PDF opens in a new tab.

  • A statement shows the qualifying work in totals by device and model, the earnings settled as payable, the amounts carried forward, held, adjusted and forfeited with their categories, the netting, any tax withheld, any Irish VAT paid with the earnings, and the payouts made. No tax is withheld: Irish law requires HIPS to withhold none from earnings.
  • With it, HIPS issues the month's self-billed invoice in your name, under the self-billing agreement of the Provider Agreement section 15.5, which you concluded when you accepted the agreement, so you do not issue your own invoice for it. A month with nothing to invoice (only netting, or a net amount of zero or less) has no invoice.
  • Each invoice bears the words "Self-billing" and a number of its own, in one sequence per year (SB-2026-000001), with your name, address and VAT number, HIPS's name, address and Irish VAT number, the date of issue, the month as the period of supply, and the supply described as GPU Time, a computation service you perform with equipment you own or control.
  • The amounts are in US dollars, with the figures in euros at the European Central Bank's euro reference rate of the day of issue, or the last one published before it.
  • Established outside Ireland, the invoice states "Reverse charge applies": HIPS accounts for the Irish VAT and adds none to your earnings. Established in Ireland and registered for VAT there, HIPS adds Irish VAT at the rate in force to your earnings once the EU's VIES service confirms your Irish VAT number, states it on the invoice in dollars and euros and pays it to you with them, and you account for it. HIPS checks the number with VIES by itself, within the hour of your giving it and again each month; months settled before it is confirmed get their VAT at the first settlement after, and an amount corrected after a settlement corrects the VAT at the next one. Established in Ireland and not registered, no VAT is shown.
  • The invoice prints the legal name and the VAT number of your payout profile, which you give under Settings (an empty VAT number field removes it), and the address your bank account's details through Stripe hold. Payouts wait for the legal name.
  • An invoice that cannot be issued yet waits, and Statements says why beside it: HIPS's Irish VAT number not set yet, the euro reference rate not in yet, or a name or address in a script the document cannot print yet. Each is issued by itself once it can be, dated that day: a name or address in another script once HIPS's documents print it, or as soon as you give it in Latin letters.

Accepting or objecting to an invoice

You have thirty days from the day an invoice is issued to accept it or object to it, and the invoice and its email give the date. On Statements, Accept the invoice confirms it; Object sends what is wrong with it, in up to 2,000 characters. Each asks you to confirm first. If you do neither by that date, the invoice is accepted: silence is acceptance. Accepting confirms the invoice's content as an invoice only; it does not limit your right to question the statement or to complain.

A person at HIPS reviews each objection and answers you by email, and the answer shows beside the invoice. Either HIPS corrects the invoice: the statement is computed again from your earnings as they stand then, an amount error fixed first by an adjustment of your earnings, with a corrective document that cancels the invoice and a new statement with a new invoice from your details as they are then, and the new invoice has thirty days of its own. Or HIPS tells you why it considers the invoice correct: you then have thirty days from the answer to accept it, after which it is accepted, and you may complain under the Provider Agreement section 16.4.

Related sheets

  • The provider Console
  • Earn with your GPU
Previous sheetProvider Console
Next sheetCrash reports
Sheet
13 of 19
Detail
E
Updated
2026-11-12
Sign in to the Console

On this sheet

  1. Four states, never one total
  2. While a new GPU is checked
  3. Holds on your earnings
  4. Batch work
  5. Work history
  6. Payouts
  7. Earnings as Credits
  8. Settlement Statements and self-billed invoices
  9. Accepting or objecting to an invoice

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ