Skip to content
Model infoModelsSnapshot: 15 Oct 2026

NTT / tsuzumi 2

tsuzumi 2 Document Vision (2026 update)

Announced revision that reads Japanese business documents as images, including tables, graphs and flowcharts. The display suffix distinguishes the update; it is not an official API identifier.

previewClosed weightsText generation
Official documentation (opens in a new tab)Reviewed 14 Oct 2026
7 of 20 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingSee billing notesNTT group (announced document-image update)
Output billingSee billing notesAccess and billing notes below

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
Not collected
Knowledge cutoff
Not collected
Release date
2026-05-19Source for Release date (opens in a new tab)

Announcement. The release says services will become available gradually; exact completed rollout remains unverified.

Parameters
Not collected
Architecture
Not collected
Languages
JapaneseSource for Languages (opens in a new tab)

Japanese document understanding is the documented focus; exhaustive locale support is not established.

Context caching
Not collected
Documented tool behavior
Improved numerical processing and interpretation of functions in technical documentsSource for Documented tool behavior (opens in a new tab)

Understanding API documentation does not establish function calling.

Hardware requirements
Single-GPU environmentSource for Hardware requirements (opens in a new tab)
Published price
Planned NTT group service rollout; no revision-specific numeric tariff verifiedSource for Published price (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.

NTT group (announced document-image update)

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

No independently callable public model selector verified for this access reference.

Access
Provider announced staged availability. No exact public selector, production endpoint, file/image limits or checkpoint version verified.
Regions
Contract, deployment and NTT group service determine availability and data 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.

NTT group (announced document-image update)

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

NTT identifies this as its proprietary, independently developed product model, distributed through commercial services and private deployments. No matching public checkpoint release was verified. Closed-weight classification is inferred for the exact product identity, not from provider ownership alone.

Classification evidence (opens in a new tab)

Lifecycle dates

Document-image update announced19 May 2026Source (opens in a new tab)

Sources reviewed