Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Preferred Networks / PLaMo

PLaMo 2.0 Prime

Inference-optimized commercial derivative of the instruction-tuned PLaMo 2.0-31B model.

historicalClosed weightsText generation
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
6 of 18 specification fields collected
Context window32K32,000 tokens
Maximum outputNot collectedAwaiting source review
Input billingSee ratesPLaMo API (historical)
Output billingSee ratesPublished units and conditions below

Specifications

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

Context / input limit
32,000 tokensSource for Context / input limit (opens in a new tab)

Approximately 32,000 in this launch source; do not infer an exact API limit.

Maximum input tokens
Not collected
Maximum output
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
Parameters
Not collected
Architecture
Not collected
Languages
JapaneseSource for Languages (opens in a new tab)

Documented focus, not a complete 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.

Base model
PLaMo 2.0-31B InstructedSource for Base model (opens in a new tab)

Access & pricing

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

API model ID
plamo-2.0-prime
Access
Earlier API revision. Retired selectors may route to a replacement model and no longer guarantee this checkpoint.
Regions
Deployment and service contract determine access and processing location.

Prices retain their published currencies and billing units below.

Published billing units · original currency · observed 14 Oct 2026
CategoryUsageRateUnit
Historical API pricingInput1¥601M tokens
Historical API pricingOutput1¥2501M tokens

Rate conditions

  1. May 2025 launch tariff. This older model is no longer served by the production PLaMo API.
Pricing source (opens in a new tab)

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 API (historical)

plamo-2.0-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)

Lifecycle dates

Announced22 May 2025Source (opens in a new tab)
2.1 automatic update announced7 Oct 2025Source (opens in a new tab)
Older PLaMo API revisions end; requests route to 3.030 Sept 2026Source (opens in a new tab)

Sources reviewed