Nixtla API
Provider source (opens in a new tab)- API model ID
timegpt-2- Access
- API key required. TimeGPT-2 variants require account access confirmation. Check /v2/models for entitlement; no live inference performed.
- Regions
- Account-specific deployment region not established
- API endpoint URL
- POST https://api.nixtla.io/v2/forecastSource for API endpoint URL (opens in a new tab)
- Authentication
- Authorization: Bearer API_KEYSource for Authentication (opens in a new tab)
- Input file formats
- JSON numeric targets y and per-series sizes; frequency freq; optional historical X, future X_future and categorical feature indices. SDK accepts pandas/polars long-format dataframes.Source for Input file formats (opens in a new tab)
- Output formats
- Numeric mean array, optional prediction intervals and feature contributions; input_tokens, output_tokens and finetune_tokens usage counters.Source for Output formats (opens in a new tab)
- Generation controls
- h > 0; prediction interval levels 0 <= level < 100. Future exogenous values must match series count × forecast horizon. No fixed numeric maximum horizon published in the schema.Source for Generation controls (opens in a new tab)
- Asynchronous processing
- POST /v2/forecast/async; poll /v2/forecast/jobs/{job_id}. Also documented: async tuning, cross-validation, anomaly detection, simulation and explanation.Source for Asynchronous processing (opens in a new tab)
- API parameters
- Additional native operations: /v2/anomaly_detection, /v2/online_anomaly_detection, /v2/cross_validation, /v2/finetune and /model_params. /v2/explain computes model-agnostic weights, not a separate foundation model.Source for API parameters (opens in a new tab)
- Billing scope
- Custom enterprise plan. Forecast responses report time-series usage counters, but exact unit conversion and rates require a quote.Source for Billing scope (opens in a new tab)
- Request quotas
- Not collected
The endpoint schema is authoritative here; older FAQ examples use a different route/header.
The dedicated requirements page and current client support polars, despite an older contradictory FAQ answer.
Numeric request, concurrency and payload quotas not established. Plans customize call limits.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
The general privacy notice explicitly excludes business API content and refers to customer agreements. Exact API retention, training use and residency remain contract-specific and unverified.
Read the service policy (opens in a new tab)