What the rental includes
PROXIES.SX Compute is an early-access marketplace for managed inference on provider-owned Apple Silicon Macs. The documented rental gives one customer a machine for 30 days through a chat-completions API. The provider runs the model through MLX. You receive API access; shell access and a remote macOS desktop are outside this product. Provider documentation
There is no per-token charge. The accepted price covers a 30-day rental; request limits still apply and the machine has finite throughput. Context length, simultaneous requests and generation length affect how much useful work it can complete. A fixed bill does not establish a latency guarantee.
Check stock before you plan a migration
On September 11, 2026, the public marketplace API returned an empty machine list. The fleet statistics returned zero online nodes. These are dated observations. Open the marketplace for current stock.
A published tier is a pricing category. A model catalog entry is a supported configuration. Neither means a machine is available to rent. Avoid scheduling a production cutover until a suitable listing exists and you can test the assigned endpoint.
From an available machine to your first request
Check the marketplace first. When a suitable ready machine exists, sign in, review its price and fund the shared USD account balance through Stripe card checkout or the cryptocurrency choices shown by CoinGate. Review the current machine quote again before confirming the rental. Currency and network choices come from hosted checkout; compute does not use x402.
The customer portal submits the expected price and pricing version. A changed quote is rejected before charge. A pending purchase is still unresolved: let the portal reconcile that operation rather than creating another purchase. A successful balance top-up alone does not allocate a Mac. Once allocation completes and the model is ready, use the rental chat endpoint. Current purchase contract
Completed purchases are non-refundable. If checkout cannot allocate the machine, its charge is reversed to account balance. Cancellation preserves access through the paid term. Renew manually for another 30 days at the displayed quote; there is no automatic renewal. Recorded outages pause remaining rental time, while a model download you request uses rental time. Dated product facts, rental operation reference
Choose with your actual workload
Take a small evaluation set from the work you intend to send. A document assistant should include long documents and questions whose answers are absent from the source. A coding assistant should include representative repository tasks and a way to check its output. Remove sensitive material from this first test.
Record the exact model ID and quantization. Then measure answer quality, time to first token and completion time at your expected concurrency. A machine that performs well for one short prompt may queue under several long requests. Use the benchmark worksheet to make comparisons repeatable.
Fit the application to the API
The customer documentation shows a rental-specific base URL and account API key. Our compute API guide explains discovery and the documented request shape. Compatibility with chat completions does not establish support for every feature in a model SDK. The current documentation rejects tools and response_format request fields. Check those limits before choosing this endpoint for an agent that depends on native tool calling or constrained output.
Run your agent orchestration and tools on infrastructure you control. The rented endpoint supplies model inference. If the agent also needs a carrier exit IP to collect web data, that is a separate proxy integration.
Work through a rental acceptance sheet
Before paying, write down the result your application must achieve. Use the following questions to decide whether a dedicated inference rental fits the job.
| Your requirement | Evidence to collect |
|---|---|
| A particular language or extraction task | Answers from your saved evaluation set using the assigned model. |
| Interactive responses | First-token and full-response timings at your busiest expected concurrency. |
| Long documents | The complete prompt and output budget, plus the endpoint's request-size limits. |
| Native tool calling | A supported request contract. The current compute docs reject tools fields. |
| Predictable spending | The full 30-day price, renewal choice and any fallback service costs. |
| Production continuity | Current stock, outage behavior and a tested application recovery path. |
Keep the acceptance sheet with the rental ID and model revision. If you change the model, repeat the quality checks before moving all traffic. A result from a different precision or revision should not silently become the approval record for the replacement.
The customer documentation says recorded offline time extends the rental term. That extension preserves paid rental time; it does not process a request while the machine is disconnected. Confirm your node's recorded extension in the dashboard, and keep an application deadline for time-sensitive jobs. Rental operation documentation
Decide what happens when a node is unavailable
The customer documentation describes a node_offline error while a machine is disconnected. Decide whether your application can wait, return a clear failure or use an independently configured fallback. Set a maximum retry period so a background job cannot wait indefinitely. Customer documentation
Dedicated tenancy identifies who shares the rented capacity. It does not establish that a machine owner cannot observe data processed on their hardware. Use the inference privacy guide to review prompt handling, retention and fallback destinations before using confidential inputs. The published retention policy allows temporary relay storage, and suppliers administer their own machines. The public materials do not establish confidential computing or a compute-specific uptime SLA.
Review the pricing calculation, then use the customer dashboard to inspect an available machine and its current terms.
Sources and references
Reviewed September 11, 2026. Product statements come from public APIs, provider documentation and published application code. Technical references explain the evaluation methods. Authenticated rental and payout behavior has not been tested.
- Dated compute product facts. PROXIES.SX.
- Compute operation and pricing reference. PROXIES.SX.
- Compute provider documentation. PROXIES.SX.
- Customer documentation in the compute application. PROXIES.SX.
- Marketplace inventory API. PROXIES.SX.
- Compute fleet statistics API. PROXIES.SX.