Auto access and benefits

From November 24, free Auto access is reserved for eligible existing recharge users and plan subscribers. Requests share idle server capacity, so queues and rate limits apply.

The free promotion ends at 00:00 Pacific Time on November 24, 2026. Users with positive net recharge completed before this cutoff retain their existing free tier. Afterward, shared free Auto is limited to these users and users with a currently effective plan. Later recharges do not grant or upgrade free benefits. Plan Auto tokens and monthly shared free benefits are separate allowances.

First free call

  1. Sign in and confirm that your account has Auto access under the eligibility rules below.
  2. Create a key that allows Auto and save the secret shown once.Open API Keys
  3. Choose your shell below and replace your-api-key with your key.
Auto

Bash on macOS, Linux or WSL requires cURL and Python 3. Keep response.json local.

export ITERACOMPUTE_API_KEY="your-api-key"

curl --fail-with-body --max-time 180 https://api.iteracompute.com/v1/chat/completions \
  -H "Authorization: Bearer $ITERACOMPUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"Auto","messages":[{"role":"user","content":"Reply with exactly: Hello!"}],"max_tokens":512,"reasoning":false}' \
  -o response.json && python3 -c 'import json; r=json.load(open("response.json")); text=r["choices"][0]["message"]["content"]; assert text and text.strip(), "Empty model reply: activation is incomplete"; print(text)'

Success means a non-empty choices[0].message.content. This command prints it and fails on an empty reply; registration or HTTP 200 alone does not complete activation. Expected output: Hello! (wording may vary).

This Auto example disables thinking for a short visible reply. 401/403: check the key and model permission. 429: check monthly usage and concurrency in the Console, then honor Retry-After. Free capacity may queue; do not fire repeated parallel retries.

One Auto model ID, multiple open models

Catalog updated: 2026-10-29.

IteraCompute allocates Auto requests according to available idle capacity. The model serving a request can change as capacity changes.

Use Auto as the model ID through the OpenAI-compatible API. Auto does not pin a particular model, version or precision, and does not guarantee identical answers or capabilities across requests. Check the Auto detail page for its current parameters and limits.

Auto input, cache-read and output token prices are $0. Monthly tokens and concurrency are shared across your account’s API keys and free routes; changing keys or model IDs does not create another allowance. Shared capacity may be slow.

Shared idle capacity, with queues and rate limits

Auto uses spare server resources rather than reserved capacity. Available capacity changes with server load; monthly token allowances do not reserve GPUs or guarantee immediate access. Requests may queue, slow down, be rate-limited or become temporarily unavailable.

Recharged tiers receive queue priority, while capacity remains shared. Speed, latency, answer quality and availability have no free-service SLA. For time-sensitive work, choose a suitable paid model and verify it against your own tasks.

Account allowances, context limits and fair-use rules still apply. Follow Retry-After when you receive a 429 response rather than sending repeated parallel requests. Auto does not provide a zero-data-retention guarantee; review the data policy before sending sensitive information.

Retained benefits for existing recharge users

Users who completed a recharge before the cutoff retain their existing tier benefits below. From November 24, new recharges do not unlock these benefits. Plan subscribers receive the Auto allowance included in their plan.

TierRecharge before the cutoffMonthly tokensContextOutput speed
FreeRecharge below $1030M128KShared capacity; may be slow
Starter$10 or more100M128KShared capacity; may be slow
Pro$50 or more300M256KShared capacity; may be slow

Free accounts may queue during busy periods. Recharged accounts receive queue priority; capacity is shared and no latency SLA is offered.

Monthly allowances count input and output, including reasoning, across all API keys on your account. Context includes input and requested output; output is capped at 8,192 tokens. There is no daily quota. Allowances reset on the first of each month at 00:00 UTC (08:00 Beijing time); unused tokens do not roll over. Requests reserve their maximum token usage before running, then settle to actual usage. There are no automatic overage charges. Requests return 429 when the monthly allowance runs out.

When your monthly allowance runs out, wait for it to reset next month. After the promotion cutoff, you can still use recharges for paid API usage, but recharges no longer grant or upgrade shared free Auto benefits. The Auto allowance included in your plan is tracked separately.

Retained tiers use USD principal from recharge orders fulfilled before the cutoff, less refunds, excluding payment fees and promotional grants. Tier changes preserve usage already consumed this month.

Read the Auto FAQ before recharging.

View plans

Setup guides for the tools you use

Start with the API quickstart, or follow the setup guide for your preferred tool. Auto’s current parameters and shared-capacity limits apply whichever client you use.

Auto questions and answers

How does free access open for new accounts?

Before the promotion ends, email verification unlocks the full 30M monthly Free allowance immediately. After the cutoff, free Auto access is limited to eligible existing recharge users and plan subscribers. Free, Starter and Pro each allow one queued or running request per account and use shared capacity that may be slow, shared across all keys and Auto. There is no daily token cap, and no call-count or UTC-date upgrade requirement. Monthly usage includes input and output; context limits, shared-capacity queues and abuse review still apply.

What happens if several accounts appear related?

Device association, registration density, request timing and verification results may require additional verification. A shared IP alone never confirms an association: offices, campuses and households may share a network. Passing a human check alone does not prove separate ownership. Only after review confirms one subject is collecting multiple trials do those accounts share one free monthly allowance and one outstanding request on shared capacity that may be slow across all keys and Auto. Contact support for review or appeal.

Are plan Auto tokens and shared free benefits the same allowance?

No. Purchased Auto tokens and monthly shared free benefits have separate quotas and usage ledgers. Plan Auto uses priority scheduling and its purchased period and contract limits. Requests use plan Auto first; uncovered requests use shared free benefits only while eligible, on shared capacity with possible queues and slower responses. Buying or renewing a plan does not reset shared free usage. When a plan expires, only users with qualifying pre-cutoff recharge retain shared free access.

Who can use free Auto after November 24?

The free promotion ends at 00:00 Pacific Time on November 24, 2026. Users with positive net recharge completed before this cutoff retain their existing free tier. Afterward, shared free Auto is limited to these users and users with a currently effective plan. Later recharges do not grant or upgrade free benefits. Plan Auto tokens and monthly shared free benefits are separate allowances.

Why can Auto requests queue or slow down?

Auto allocates shared idle server resources. Capacity varies with server load, so requests may queue, slow down, be rate-limited or become temporarily unavailable. Recharge tiers receive queue priority, not reserved GPUs or a speed or latency guarantee.

Does Auto always use the same model and precision?

Auto allocates each request according to available idle capacity. The model, version and precision can vary. See the Auto detail page for current parameters.

Does recharging increase the Auto allowance?

For users who recharged before the cutoff, cumulative net recharge of $10 qualifies for Starter: 100M tokens/month and 128K context. At $50, Pro provides 300M tokens/month and 256K context. Both receive queue priority. Recharging above $50 does not automatically add free-model benefits. Recharge remains spendable API balance; these thresholds are not monthly fees. Only principal from orders fulfilled before the cutoff counts; later recharges cannot raise these tiers. Refunds still reduce the qualifying net principal.

What benefits do recharged users retain?

For eligible pre-cutoff recharge users, lifetime benefits mean retaining the monthly token allowance, context limit and queue priority of the Starter or Pro tier they have reached, including after a free-model upgrade or replacement. Spending the balance does not lower the tier; refunds may change it and abuse rules still apply. This does not freeze a model name, weights or precision, or promise unlimited usage, dedicated capacity or permanent service availability.