Platform conversations are metered per call minute from a prepaid balance. The conversation dashboard reports minutes, cost per minute and total cost. The exact enterprise voice-agent tariff and any additional charges require the plan/order form.Source for Usage metering (opens in a new tab)
Published price
Platform account top-ups are in USD with a $5 minimum. This is account funding, not a per-call price or minimum inference charge. No numeric agent-minute rate is published in the reviewed pages.Source 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.
Task route and language code are not immutable checkpoint selectors.
Access
Enterprise deployment by agreement; no reviewed public agent-creation route, native checkpoint selector or per-call tariff.
Regions
Policy describes international processing; exact inference region is not specified.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Privacy permits processing audio, transcripts, call metadata and usage logs; recordings/transcripts may be retained on enterprise customer instruction. No training on enterprise call content for general-purpose models without written customer instruction; policy separately describes speech and agent quality improvement. Retention depends on purpose and customer instructions, with no fixed TTL. Cloud, telephony, speech-processing and analytics providers may process data across regions. This is not universal zero retention or a blanket no-training guarantee.
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.
Pindo enterprise telephony
Not verified
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
How it works
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
Minimum reusable input
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
Lifetime & refresh
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
How to enable it
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
Usage fields
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
Billing rules
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
Limits & data boundaries
Not collected
No inference-cache contract published in reviewed sources. Uploaded/generated file storage and call recording retention are not prompt caching.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 16 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
Proprietary hosted service; Pindo and its licensors reserve service/model IP and restrict reverse engineering. Specific checkpoint identity and artifact licensing are undisclosed, so this is not claimed as an independently verified closed-weight release.
