Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Preferred Networks / PLaMo

PLaMo Fin Base

Commercial financial-domain base model with additional Japanese finance training, preceding the aligned Fin Prime model.

historicalClosed weightsText generation
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
5 of 17 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedPFN financial enterprise deployments
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 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
SupportedSource for Fine-tuning (opens in a new tab)

Provider-assisted domain adaptation, not a self-service API.

Knowledge cutoff
Not collected
Parameters
Not collected
Architecture
Not collected
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.

PFN financial enterprise deployments

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

Display or catalog name is not a verified API request selector.

Access
Sales-assisted private deployment; current availability of this original base checkpoint needs confirmation.
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.

PFN financial enterprise deployments

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

Japanese Financial Evaluation Harness

Preferred Networks · vendor-reported
59provider aggregate score

Five Japanese finance tasks; provider on-premise likelihood evaluation, June 2025 table.

Evaluation source (opens in a new tab)

Preferred Multi-turn Benchmark for Finance in Japanese

Preferred Networks · vendor-reported
7.08score / 10

Provider evaluation over 360 dialogues across twelve task types, June 2025 table.

Evaluation source (opens in a new tab)

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

Announced27 Jan 2025Source (opens in a new tab)

Sources reviewed