Discover the product without credentials
These public endpoints support credential-free discovery. None of the following reads creates a rental, starts inference or sends a payment.
curl --fail --show-error https://api.proxies.sx/v1/peer/compute/catalog
curl --fail --show-error https://api.proxies.sx/v1/peer/compute/tiers
curl --fail --show-error https://api.proxies.sx/v1/peer/compute/marketplace
curl --fail --show-error https://api.proxies.sx/v1/peer/compute/stats
The responses contain models, tiers and machines arrays, with fleet state in the stats response. Treat an empty machine list as no visible rental supply. Do not substitute the tier list for inventory. Validate the response shape and handle network errors before an automated workflow makes a decision.
This site's compute index supplies page links and product references as JSON. The plain-text guide contains the same editorial material as these HTML pages. They are convenience formats; the live product API is the authority for stock and catalog changes.
Use the rental-specific endpoint
The customer documentation and its published client example use this base URL:
https://api.proxies.sx/v1/peer/compute/rentals/<rentalId>
Create a key on the renter API page with compute:read and compute:infer scopes. Both X-API-Key: <key> and Authorization: Bearer <key> are accepted. The OpenAI SDK's api_key or apiKey option sends the supported Bearer header. Set the rental-specific base URL, and use the rental ID and assigned model from your existing deployments. Example request:
# Set COMPUTE_RENTAL_ID and COMPUTE_API_KEY from your account.
# Replace the example model with the model assigned to your rental.
curl --fail-with-body --show-error --max-time 190 \
"https://api.proxies.sx/v1/peer/compute/rentals/${COMPUTE_RENTAL_ID}/chat/completions" \
-H "X-API-Key: ${COMPUTE_API_KEY}" \
-H 'Content-Type: application/json' \
--data '{"model":"qwen3.8-27b-4bit","messages":[{"role":"user","content":"Reply with hello."}],"max_tokens":32,"stream":false}'
Keep credentials on your application server or in its secret store. A public browser bundle or a pasted conversation is not an appropriate place for an account key. Consult the customer dashboard for key management.
Test the features your agent needs
Start with a short response, then test streaming and your real prompt lengths. The current customer documentation explicitly rejects tools, stop sequences and response_format with HTTP 400. An agent requiring those request fields needs a supported alternative or a different application design. Chat completions do not imply an embeddings endpoint. Documented request contract
Run the orchestration loop and external tools on your own system. The rented model endpoint returns model output. For document applications, the RAG hosting guide maps retrieval, source checks and generation to their respective components. A host's larger memory does not automatically make its model reliable at choosing tools or following a schema.
Bound retries and queue growth
Handle node_offline, model_not_ready, node_not_approved, rental_expired and queue_full according to the reported state. Management operations can also return node_busy, node_rented or benchmark_in_flight; do not work around those allocation guards. Use bounded backoff, an application deadline and a queue limit. A 429 requires backoff; a 504 or incomplete/error SSE stream is a failed request, even if some text arrived. Keep prompt text and credentials out of routine error logs.
Enforce the published request limits
The managed endpoint supports text chat completions within these limits. It does not expose all options from a generic model SDK.
| Field or condition | Documented behavior |
|---|---|
messages | 1–64 text messages with system, user or assistant roles; each content string is limited to 65,536 characters by validation. |
max_tokens | 1–4096; default 1024. |
| Other supported fields | model, temperature from 0–2, stream. |
| Streaming | Server-sent events. |
| Request deadline | API default 180 seconds; agent generation deadline 175 seconds and idle-output limit 60 seconds. |
| Endpoint throttle | 60 requests per minute by client IP and handler; additional per-key/account limits may apply. |
| Unsupported generation options | Tools, stop sequences, response_format and other unsupported options return HTTP 400. |
| Expired, offline or unready rental | HTTP 409 with a specific error code. |
A conservative input-byte check also requires the total UTF-8 content bytes, plus 64 per message, plus 256 for formatting, plus the requested output-token cap, to fit the catalog context limit. The per-message and message-count limits are not permission to send their product as one prompt. Bytes and tokens differ: a prompt within a tokenizer-based budget can still fail this stricter input check. Shorten the text or output cap and handle that rejection explicitly. Customer request documentation
One job runs at a time on each node. Bound concurrent work in your application and expect queueing or rejection at capacity. The throttle is not independent capacity per key or rental, and does not imply that sixty long requests finish every minute. Streaming uses server-sent events; images/audio, embeddings, native tool calling and the Responses API are unsupported. Use the benchmark method to establish useful throughput.
Keep purchase permissions separate from inference
An inference key needs compute:read and compute:infer according to the customer docs. Programmatic checkout and renewal additionally require compute:purchase and an Idempotency-Key header containing 8–128 letters, digits, dashes or underscores. Reuse the same operation key and request after a timeout or operation_pending; a new purchase intent gets a new operation key. Customer checkout documentation
Model changes and cancellation require compute:manage. Keys created on the renter API page only grant read and inference; they cannot spend or manage rentals. Supplier keys use account:read and compute:supply with a farmer account, while the installed agent manages a separate device JWT. Never give a renter a supplier or admin key. Keep spending credentials outside the model prompt and enforce authorization in application code.
Handle a changed quote differently from a pending purchase
Send expectedPriceUsd and pricingVersion from the current machine quote, as the customer portal does, so a changed price is rejected before charge. Existing rentals expose their current renewalQuote through GET /v1/peer/compute/rentals/mine. Renewal is an explicit purchase for another 30 days. This website hands checkout to the customer portal. Purchase and renewal contract
| State | What an integration should do |
|---|---|
Request timed out or operation_pending | Retry the existing intent with its original body and idempotency key. |
Terminal 409 price_changed | No charge occurs for the stale quote. Refresh the quote, obtain confirmation and create a new intent key. |
| Allocation fails | Check the operation result and balance reversal; a funded balance alone does not mean a rental exists. |
| Rental committed | Use the returned rental and assigned model. The accepted price and split stay fixed for that intent. |
Never replace the body of an unresolved intent with a newer quote. Resolve it first. Treat a confirmed rental operation as the purchase result; a CTA click or top-up redirect is not proof of a purchase.
Proxy payments are a separate integration
The existing x402 guide documents purchasing proxy resources. It does not establish an x402 compute checkout or compute tools in the proxy MCP server. Use the compute customer flow for rentals and review its current terms. The agent proxy guide remains relevant when an agent needs network access as well as model inference.
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.
- Current compute product reference. PROXIES.SX.
- Compute operation and pricing reference. PROXIES.SX.
- Customer documentation in the compute application. PROXIES.SX.