Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Reka / Reka Spark

Reka Spark

Small embedded multimodal model offered for vehicle and telematics deployments.

Robotics / embodied reasoning
restrictedClosed weightsEmbodied reasoning
Official documentation (opens in a new tab)Reviewed 13 Oct 2026
4 of 18 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedReka embedded deployment
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
Not collected
Maximum output
Not collected
Input modalities
Video, Audio, Sensor dataSource for Input modalities (opens in a new tab)

Capabilities described for the automotive solution; exact tensor formats and model boundaries are not specified.

Output modalities
Not collected
Reasoning
Not collected
Tool calling
Not collected
Structured output
Not collected
Streaming
Not collected
Batch processing
Not collected
Fine-tuning
Not collected
Knowledge cutoff
Not collected
Release date
Not collected
Parameters
1 billion parametersSource for Parameters (opens in a new tab)
Architecture
Not collected
Languages
Not collected
Context caching
Not collected
Deployment targets
Automotive SoCs, dashcam ECUs and fleet gateway devicesSource for Deployment targets (opens in a new tab)
Provider-reported latency
Provider claims sub-80 ms on embedded production-class hardwareSource for Provider-reported latency (opens in a new tab)

No hardware configuration, workload distribution or independent timing established.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

Reka embedded deployment

Provider source (opens in a new tab)
API model ID
Not collected

An exact current checkpoint selector is not established by the reviewed documentation.

Access
Confirm release-specific access and deployment terms with Reka; a historical announcement does not establish current public API availability.
Regions
Serving-region and residency guarantees require a release-specific agreement.

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Reka embedded deployment

Not verified
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected

No verified cache rate for this endpoint. An empty rate is not a zero charge.

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Release-specific inference from the provider’s proprietary-model documentation, native research/service descriptions and public-weight inventory. No weight release for this exact identity was found. Open Edge 2603, Flash 3/3.1 and Inverse Dynamics Model releases are excluded. Historical family names are not equated with later open checkpoints.

Classification evidence (opens in a new tab)

Sources reviewed