Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Preferred Networks / PLaMo

PLaMo 3.1 Prime (development reference)

Named in the provider’s development documentation; a production launch or generally available service is not verified.

previewClosed weightsText generation
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
5 of 17 specification fields collected
Context window262.1K262,144 tokens
Maximum output20.5K20,480 tokens
Input billingNot collectedPLaMo development documentation
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.

Maximum input tokens
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
Not collected
Architecture
Not collected
Languages
Not collected

Development API reference does not establish a model-specific language inventory.

Context caching
Not collected

No model-specific public prompt-cache contract or cached-token discount was verified. Internal inference caches do not establish a customer-facing cache feature.

Access & pricing

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

PLaMo development documentation

Provider source (opens in a new tab)
API model ID
plamo-3.1-prime
Access
Documentation-only evidence. Do not assume this selector is accepted by the production API or copy 3.0 pricing.
Regions
Deployment and service contract determine access and processing location.

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.

PLaMo development documentation

plamo-3.1-prime
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.

Caching reviewed 14 Oct 2026

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

Named provider model offered through commercial services, private licensing or provider research, with no matching public checkpoint verified. Closed-weight classification is inferred for this specific derivative, not its public base or other PLaMo releases.

Classification evidence (opens in a new tab)

Sources reviewed