Read the effective machine quote
Admin controls tier defaults, per-node overrides and the platform/farmer split. The tiers API exposes defaults. The effective machine price and pricing version in the marketplace API determine the current node quote. A farmer price proposal has no effect until admin approves it.
| Tier | Minimum RAM | Price to use |
|---|---|---|
| Starter | 24 GB | Current approved quote for the selected node. |
| Pro | 48 GB | Current approved quote for the selected node. |
| Max | 96 GB | Current approved quote for the selected node. |
Choose a supported model at Models, then review its compatible machines and quote. Billing covers 30 days, with no per-token charge; request limits and finite capacity apply. Dividing a quote by 720 hours is comparison arithmetic, not an hourly purchase option. A tier price does not prove a machine is in stock.
Calculate the alternative token bill
Use input and output tokens separately because their prices can differ. Include any cache discounts or extra charges from the provider you are comparing.
token bill = (input tokens / 1,000,000 × input price)
+ (output tokens / 1,000,000 × output price)
dedicated cost per million output tokens
= rental price / delivered output tokens × 1,000,000
For a purely hypothetical API charging $1 per million input tokens and $3 per million output tokens, 50 million input and 10 million output tokens cost $80. An assumed $300 rental costs more under those assumptions; use the approved machine price for your own comparison. At 200 million input and 50 million output tokens, the hypothetical bill is $350. These are worked examples, not a competing provider's quote or a claim that the Mac can deliver those volumes.
The second formula allocates the whole rental bill to output for comparison. It is not a price PROXIES.SX charges per token. Input processing still consumes capacity even when the rental bill stays fixed.
Check whether the workload fits into 30 days
Suppose your own test measures 10 output tokens per second. Producing 10 million output tokens would take about 278 hours of decoding alone. This excludes time spent reading prompts, loading models, waiting for work and recovering from errors. Ten tokens per second is an illustrative input, not a measured PROXIES.SX result.
Do this calculation using your own benchmark. A theoretical price saving has little value if work misses its deadline or needs a second provider to handle peaks. Include that fallback bill in the comparison.
Compare equivalent work
Two APIs with the same chat-completions request shape can serve different models. Compare answer quality before cost. A cheaper response that fails your extraction checks or breaks the agent's tool selection is not equivalent output.
Also compare what you manage. A bare-metal Mac rental can include operating-system access and require you to install the model service. PROXIES.SX's documented product supplies a managed inference endpoint. The cloud comparison explains how to separate those buying decisions.
Calculate cost per accepted result
Use successful work as the denominator when the model's output must pass a check. For example, an assumed $300 rental that delivers 10,000 usable extractions allocates $0.03 to each accepted extraction. If only 8,000 pass, the figure becomes $0.0375. These are arithmetic scenarios; neither volume has been measured on this service.
Include retries and rejected outputs in the work the node must process. Keep the acceptance rule fixed when comparing services. Otherwise, an API can appear cheaper simply because you allowed it to return less accurate work.
For a batch job, compare the expected number of attempts with the successful request rate measured in your benchmark. For interactive work, retain a latency target as well. A 30-day period with plenty of spare capacity can still have a peak hour that fails the application.
Completed rentals are non-refundable. A checkout that cannot allocate a machine is automatically reversed to account balance. Cancellation preserves access through the paid term. Read the current checkout terms and operation result before treating a payment as a rental. Published rental terms
Confirm the term in the dashboard
Renewal is manual. Top up the shared USD balance through Stripe card checkout or the CoinGate currencies and networks offered at checkout, then explicitly purchase another 30 days at the current quote. Check suitable stock before funding a new compute purchase. A balance top-up is not a rental and does not reserve a machine.
The portal submits expectedPriceUsd and pricingVersion with an Idempotency-Key. A timeout or operation_pending must be reconciled with the identical request and key. A terminal price_changed means no charge for that stale quote: review a fresh quote and start a new intent. Accepted purchases and renewals preserve their recorded price and split; later renewals need a new quote. Recorded outages pause remaining rental time, including past the original expiry. A customer-requested model download uses rental time. Current pricing and renewal contract
If you are supplying the Mac, the rental price is customer revenue before the provider share and operating costs. Use the separate provider calculation.
Sources and references
Product reviewed September 16, 2026 against public APIs, provider documentation and application code. External technical references explain the evaluation methods and retain their original publication dates. This guide review did not run a paid rental or payout.
- Compute operation and pricing reference. PROXIES.SX.
- Customer documentation in the compute application. PROXIES.SX.
- Rental tiers API. PROXIES.SX.
- Marketplace inventory API. PROXIES.SX.