Build chat, summarization and explanation prototypes with text and bounded document or code excerpts.
- Tool calling
ApoyadoLlamada de herramientas · Apoyado
- Reasoning
ApoyadoRazonamiento · Apoyado
- Vision
ApoyadoVisión · Apoyado
- Streaming
ApoyadoTransmisión · Apoyado
- JSON mode
ApoyadoModo JSON · Apoyado
USD / 1M tokens
- Input
- $0.00
- Cache read
- $0.00
- Cache write
- —
- Output
- $0.00
- Context
- 256K
- Max output
- 8K
- Price checked
Model availability and prices
Overview
IteraCompute asigna las solicitudes según la capacidad libre disponible. Usa Auto como ID del modelo.
- Input / output
- text, image / text
- Endpoint
- /v1/chat/completions
API protocols and integration
- Base URL · OpenAI SDK
https://api.iteracompute.com/v1- Authentication
Authorization: Bearer ITERACOMPUTE_API_KEY
Choose request fields, response parsing and stream completion by endpoint. This table describes wire formats; see this model's capabilities and verification scope.
| Customer endpoint | Model status | Input / output budget | Result | SSE completion |
|---|---|---|---|---|
OpenAI Chat CompletionsPOST /v1/chat/completions | Declared for this model | messagesmax_tokens | choices[0].message.content | [DONE] |
OpenAI ResponsesPOST /v1/responses | Not declared; acceptance pending | inputmax_output_tokens | output[] (SDK: output_text) | response.completed |
Anthropic MessagesPOST /v1/messages | Not declared; acceptance pending | messages; system (top-level)max_tokens (required) | content[] | message_stop |
For the Messages SDK use https://api.iteracompute.com as base URL; max_tokens is required. Do not reuse another protocol's fields.
Tabla por nivel · Ejemplo de configuración de Roo Code
LLMs.txt · Copy for an AI coding assistant
Includes this model's ID, wire formats and parameter constraints. Check this page's verification scope and current prices before use.
# IteraCompute · Auto
Model ID: Auto
Base URL (OpenAI SDK): https://api.iteracompute.com/v1
Authentication: Authorization: Bearer ITERACOMPUTE_API_KEY
Content-Type: application/json
Use only the customer endpoints below. Request and response formats differ by protocol. An endpoint declaration does not certify every capability.
## Chat Completions
POST https://api.iteracompute.com/v1/chat/completions
Input: messages
Output budget: max_tokens
Read result: choices[0].message.content
SSE completion: [DONE]
Docs: https://iteracompute.com/docs.html#api-reference
Auto uses idle server resources and shared free-model allowances. Speed, latency and response quality are not guaranteed. No ZDR guarantee.
## Auto access eligibility
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.
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.
Recharge eligibility uses positive net principal from orders fulfilled before 2026-11-24T08:00:00Z; later recharges cannot raise the retained free tier. Existing usage and admitted requests are preserved.
Límite de contexto del modelo: 262144 tokens
El contexto total incluye los tokens de entrada y los reservados para la salida.
Free / Starter: 131072 tokens en total. Pro: 262144 tokens en total. Cada plan de pago tiene sus propios límites de contexto.
Tabla por nivel: https://iteracompute.com/es/free/#auto-tiers
Ejemplo de configuración de Roo Code: https://iteracompute.com/es/integrations/roo-code/?model=Auto#roo-fields
## Parameters
Configuration and parameter acceptance do not establish semantic capability. Do not invent undisclosed defaults.
Parameter revision: 0ad2609481be7694d5d65bf409f949909b910d843bdc63357309a2664f705e7c
Maximum output tokens: 8192
Capability tools: configured enabled (see verification scope)
Capability reasoning: configured enabled (see verification scope)
Capability vision: configured enabled (see verification scope)
Capability streaming: configured enabled (see verification scope)
Capability json_mode: configured enabled (see verification scope)
- max_tokens: integer; accepted; min=1; max=8192; default=Undisclosed. Output token budget; includes reasoning where applicable. Chat Completions / Messages.
- max_completion_tokens: integer; accepted; min=1; max=8192; default=Undisclosed. Alternative Chat output budget; use only when accepted by this model.
- max_output_tokens: integer; unsupported; min=1; max=8192; default=not applicable. Responses output budget. Chat acceptance must be checked separately.
- temperature: number; accepted; min=0; max=2; default=Undisclosed. Sampling randomness. An accepted but ignored value does not control generation.
- top_p: number; accepted; min=0 (exclusive); max=1; default=Undisclosed. Nucleus sampling probability threshold.
- presence_penalty: number; accepted; min=-2; max=2; default=Undisclosed. Penalize tokens already present in the generated text.
- frequency_penalty: number; accepted; min=-2; max=2; default=Undisclosed. Penalize repeated tokens according to frequency.
- n: integer; accepted; min=1; max=1; default=Undisclosed. Number of completions; many routes accept only 1.
- stream: boolean; accepted; min=unknown; max=unknown; default=Undisclosed. Enable SSE streaming; completion markers depend on the protocol.
- tools: array; accepted; min=unknown; max=unknown; default=Undisclosed. Tool definitions; the application executes tool calls and returns results.
- tool_choice: any; accepted; min=unknown; max=unknown; default=Undisclosed. Choose whether and which tool to call; allowed shapes vary by protocol.
- response_format: object; accepted; min=unknown; max=unknown; default=Undisclosed. Text: Chat output format. Images: b64_json only; not text JSON mode.
- reasoning: any; accepted; min=unknown; max=unknown; default=Undisclosed. Reasoning control; object or boolean depends on the model and protocol.
- reasoning_effort: enum; accepted; values=["none","low","medium","xhigh"]; default=xhigh. Chat reasoning effort; use the model's listed values, not another protocol's shape.
## Chat Completions example · JSON body
```json
{
"model": "Auto",
"messages": [
{
"role": "user",
"content": "Reply OK"
}
],
"max_tokens": 256,
"reasoning_effort": "low"
}
```
## References
Model catalog: https://iteracompute.com/models/
Current prices and billing: https://iteracompute.com/pricing/
Documentation index: https://iteracompute.com/llms.txt
Unknown prices are not zero. Account and subscription limits also apply.
Never include a real API key in an LLM prompt or client-side code.
API parameters
- Model IDs are case-sensitive: use Auto. The version identifies the routing configuration, not model weights.
- Context includes input and the requested maximum output. The stricter route or account-tier limit applies; see the parameter limits for maximum output.
- Default thinking requires an output budget of at least 128 tokens; explicitly disabling thinking permits values from 1. The low, medium and xhigh compatibility values enable thinking on the current backend; separate intensity levels have not been established.
- Input, cache-read and output retail rates are USD 0 per million tokens. An unknown cache-write price is shown as —, not zero.
- Tools, reasoning output, two-color image recognition, JSON parsing and streaming text/usage/end markers passed on Auto. Future routes require fresh acceptance and human approval.
- These examples use Chat Completions. Set the output budget with max_tokens or max_completion_tokens; max_output_tokens is not accepted.
These parameters and ranges describe the current route. Account and context limits also apply. Parameter acceptance does not establish model capability.
- Tool calling
- Supported
- Reasoning
- Supported
- Vision
- Supported
- Streaming
- Supported
- JSON mode
- Supported
Parameters and values
Click a parameter to copy its name; scroll the table horizontally to see all columns. Usage notes identify protocol differences; identical names do not guarantee cross-endpoint support.
| Parameter | Type | Acceptance | Range | Usage / protocol |
|---|---|---|---|---|
| integer | Accepted | [1, 8192] | Output token budget; includes reasoning where applicable. Chat Completions / Messages. | |
| integer | Accepted | [1, 8192] | Alternative Chat output budget; use only when accepted by this model. | |
| integer | Unsupported | [1, 8192] | Responses output budget. Chat acceptance must be checked separately. | |
| number | Accepted | [0, 2] | Sampling randomness. An accepted but ignored value does not control generation. | |
| number | Accepted | (0, 1] | Nucleus sampling probability threshold. | |
| number | Accepted | [-2, 2] | Penalize tokens already present in the generated text. | |
| number | Accepted | [-2, 2] | Penalize repeated tokens according to frequency. | |
| integer | Accepted | [1, 1] | Number of completions; many routes accept only 1. | |
| boolean | Accepted | — | Enable SSE streaming; completion markers depend on the protocol. | |
| array | Accepted | — | Tool definitions; the application executes tool calls and returns results. | |
| any | Accepted | — | Choose whether and which tool to call; allowed shapes vary by protocol. | |
| object | Accepted | — | Text: Chat output format. Images: b64_json only; not text JSON mode. | |
| any | Accepted | — | Reasoning control; object or boolean depends on the model and protocol. | |
| enum | Accepted | ["none","low","medium","xhigh"] | Chat reasoning effort; use the model's listed values, not another protocol's shape. |
Current configuration example
POST /v1/chat/completions
{
"model": "Auto",
"messages": [
{
"role": "user",
"content": "Reply OK"
}
],
"max_tokens": 256,
"reasoning_effort": "low"
}Parameter revision:0ad2609481be
Technical reference (current configuration takes precedence)
Parámetros API
Haz clic en un parámetro para copiar su nombre.
Auto[{"role": "user", "content": "Hello!"}]
Las capacidades adicionales y los parámetros específicos del modelo no se han verificado en esta ruta. Prueba las funciones necesarias antes de usarlas en producción.
API
import os
from openai import OpenAI
client = OpenAI(
base_url="https://api.iteracompute.com/v1",
api_key=os.environ["ITERACOMPUTE_API_KEY"],
)
response = client.chat.completions.create(
model="Auto",
messages=[
{
"role": "user",
"content": "Reply OK"
}
],
max_tokens=256,
reasoning_effort="low",
)
print(response.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api.iteracompute.com/v1",
apiKey: process.env.ITERACOMPUTE_API_KEY,
});
const response = await client.chat.completions.create({
"model": "Auto",
"messages": [
{
"role": "user",
"content": "Reply OK"
}
],
"max_tokens": 256,
"reasoning_effort": "low"
});
console.log(response.choices[0].message.content);curl 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 OK"
}
],
"max_tokens": 256,
"reasoning_effort": "low"
}'Precios
Los precios y la disponibilidad actuales se muestran abajo. Un precio desconocido no significa que sea gratis.
- Model ID
Auto- Context
- 256K
- Price checked
- Verification scope and sources
View verification scope and sources
2026-11-10 · Auto passed bounded real-model tests for text, tool calls, observable reasoning, two-color image recognition, JSON and streaming. Full-context quality, long-run performance and arbitrary-task accuracy were not evaluated.
Fuente del precio: API pública de modelos · Los precios y la precisión se verifican por separado.
Las tarifas de lectura de caché se aplican a aciertos reales. Una tarifa ausente (—) es desconocida, no cero. Consulte los límites de uso para las restricciones de contexto de la cuenta y del Gateway.
Usage limits
- Free capacity is shared and may queue during busy periods. Speed, latency, output quality and availability have no SLA.
- The underlying model may change with resource availability. Evaluate paid models separately for tasks that require consistent quality or performance.
- Account allowances, concurrency and context restrictions apply together. Changing API keys or model IDs does not add allowance, and exhausted free quota does not become a paid request automatically.
- Capability checks cover controlled tool, reasoning, color-recognition and JSON cases. They do not establish reliability for arbitrary tasks or full-context inputs.
- The free service does not promise zero data retention. Follow the data policy and avoid submitting data unsuitable for this service.
Use cases
Connect structured tool calls, JSON replies and image questions using the verified common capabilities of the current pool.
Integrate standard SDKs and streaming responses, and evaluate application behavior with shared free capacity.
Elige tu herramienta
Elige un modelo y herramienta para tu tareaAsignación gratuita y límites
Preguntas frecuentes
¿Cómo uso Auto con el SDK de OpenAI?
Establezca base_url en https://api.iteracompute.com/v1 y modelo en Auto.Autentíquese con su clave API de IteraCompute.
¿Cuánto cuesta Auto?
Consulte los precios en tiempo real para conocer las tarifas y la disponibilidad actuales. Las llamadas con tarifa cero confirmada consumen la cuota compartida de modelos gratuitos; agotarla no convierte las solicitudes automáticamente en llamadas de pago. Se aplican límites de uso justo y la capacidad gratuita no tiene SLA. Los precios desconocidos o no admitidos de escritura en caché se muestran por separado.
¿Qué longitud de contexto está disponible?
Consulte el resumen anterior para ver el contexto y la salida máxima de esta API. La entrada y la salida solicitada comparten el presupuesto de contexto. Free: contexto total de 128K y 30M tokens/mes. Tras $10 de recarga neta acumulada, Starter ofrece 100M tokens/mes y contexto de 128K; tras $50, Pro ofrece 300M tokens/mes y contexto de 256K. Ambos niveles recargados tienen prioridad en la cola. Los tres niveles permiten una solicitud en cola o en generación por cuenta entre todas las claves y rutas gratuitas, sin límite de tokens diarios. La salida máxima es de 8,192 tokens en todos los niveles; el contexto incluye la entrada y la salida máxima solicitada. La capacidad compartida puede generar esperas o lentitud.
¿Listo para su primera solicitud?
Cree su clave, elija una herramienta y obtenga una primera respuesta que no esté vacía.
Beneficios conservados para usuarios que ya recargaron
Quienes completaron una recarga antes del cierre conservan los beneficios de su nivel que se indican a continuación. Desde el 24 de noviembre, las nuevas recargas no los otorgan. Los suscriptores reciben la cuota de Auto incluida en su plan.
| Nivel | Recarga anterior al cierre | tokens mensuales | Contexto | Velocidad de salida |
|---|---|---|---|---|
| Gratis | Recarga inferior a $10 | 30M | 128K | Capacidad compartida; puede ser lenta |
| entrante | $10 o más | 100M | 128K | Capacidad compartida; puede ser lenta |
| profesional | $50 o más | 300M | 256K | Capacidad compartida; puede ser lenta |
Las cuentas gratuitas pueden hacer cola durante los períodos de mayor actividad.Las cuentas recargadas reciben prioridad en la cola;la capacidad se comparte y no se ofrece SLA de latencia.
Las asignaciones mensuales cuentan las entradas y salidas, incluido el razonamiento, en todas las claves API de su cuenta.El contexto incluye entradas y salidas solicitadas;La producción tiene un límite de 8.192 tokens.No hay cuota diaria.Las asignaciones se restablecen el primero de cada mes a las 00:00 UTC (08:00 hora de Beijing);Las tokens no utilizadas no se acumulan.Las solicitudes reservan su uso máximo de token antes de ejecutarse y luego se ajustan al uso real.Sin excedente pagado automáticamente: la cuota mensual agotada devuelve 429.
Cuando se agote tu cuota mensual, espera a que se restablezca el próximo mes. Una vez finalizada la promoción, puedes seguir usando las recargas para pagar el uso de la API, pero las recargas ya no otorgan ni mejoran los beneficios compartidos de Auto gratuito. La cuota de Auto incluida en tu plan se contabiliza por separado.
Los niveles conservados se calculan con el principal en USD de recargas acreditadas antes del cierre, menos reembolsos y sin comisiones ni promociones. Los cambios de nivel conservan el uso ya consumido este mes.
Lee las preguntas frecuentes sobre Auto antes de recargar.
Ver planesNuevos modelos
Explora los modelos seleccionados como novedades, con precios de API, funciones compatibles y guías de integración.
Gemini 4 Hydrogen
gemini/gemini-4-hydrogen
Google Cloud lists Gemini 4 Hydrogen for fast coding assistance, multimodal input and high-volume text generation.
Disponible en IteraCompute desde
- Entrada
- $1.50
- Salida
- $7.50
USD / 1 millón de tokens
GPT-6.2 Astra
openai/gpt-6.2-astra
OpenAI lists GPT-6.2 Astra for complex engineering and long-horizon reasoning.
Disponible en IteraCompute desde
- Entrada
- $8.00
- Salida
- $40.00
USD / 1 millón de tokens
GPT-6.2 Sol
openai/gpt-6.2-sol
OpenAI lists GPT-6.2 Sol for everyday coding and agent workflows.
Disponible en IteraCompute desde
- Entrada
- $2.00
- Salida
- $10.00
USD / 1 millón de tokens