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
No reviewed model-specific value. Unknown is not unsupported.
Maximum input tokens
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Maximum output
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Parameters
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Release date
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Knowledge cutoff
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Tool calling
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Structured output
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Streaming
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Batch processing
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Fine-tuning
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Reasoning
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Context caching
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Base model
Not collected
No reviewed model-specific value. Unknown is not unsupported.
Published price
Dev Pass: USD 9.99/month with 1,000 API calls. Public pricing lists SMME Pass at USD 49.99/month with 10,000 calls; plan documentation instead lists USD 49/month. Confirm at checkout. Enterprise is quoted, with 500,000+ calls described. These are subscription allowances, not token or marginal per-call rates.Source for Published price (opens in a new tab)
Pricing discrepancy
SMME price differs between public pricing (USD 49.99) and plan docs (USD 49). Enterprise marketing says no rate limits; technical plan docs say custom limits. Do not infer unlimited concurrency or an unconditional request quota.Source for Pricing discrepancy (opens in a new tab)
Request quotas
Per project: Free and Dev 60 requests/minute; SMME 120/minute; Enterprise custom. Keys in one project share quotas. Free allowance is 100 calls/month; monthly limits reset on the first day UTC. Only successful calls count for billing.Source for Request quotas (opens in a new tab)
Intended for telephone or meeting audio with modest speaker counts. The card warns about more than four speakers and separately describes a 3–5-speaker range.Source for Speaker attribution (opens in a new tab)
Quality guidance is not a hard API speaker limit.
Access & pricing
Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.
Routes select languages or product features rather than exposing an immutable model ID.
Access
POST https://api.lelapa.ai/v1/transcribe/sync. X-CLIENT-TOKEN authentication; documented keys expire after 90 days. Set diarise=true within transcription.
Regions
Model-specific processing location not established in reviewed sources.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
The May 2026 privacy notice says client data is not used for model training. Audio and transcripts follow the customer data-processing agreement; processing logs follow a separate retention policy. No universal numerical retention period or zero-retention guarantee is published. Service subprocessors are covered by data-processing agreements. Software rights remain with Lelapa; customers retain rights to outputs.
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.
Lelapa Vulavula API
Not verified
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
How it works
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
Minimum reusable input
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
Lifetime & refresh
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
How to enable it
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
Usage fields
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
Billing rules
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native prompt caching.
Limits & data boundaries
Not collected
No reviewed model inference-cache contract. Browser cookies, credentials, quota refill and stored transcripts are not native 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
AMI DER
Lelapa AI · provider-reported
8.69%
Published model-card evaluation, not independently reproduced and not a guarantee for current routing or different recordings. Version 1.0.0. Lower diarization error rate is better; speaker counts and overlap differ by dataset.
Published model-card evaluation, not independently reproduced and not a guarantee for current routing or different recordings. Version 1.0.0. Lower diarization error rate is better; speaker counts and overlap differ by dataset.
Published model-card evaluation, not independently reproduced and not a guarantee for current routing or different recordings. Version 1.0.0. Lower diarization error rate is better; speaker counts and overlap differ by dataset.
Published model-card evaluation, not independently reproduced and not a guarantee for current routing or different recordings. Version 1.0.0. Lower diarization error rate is better; speaker counts and overlap differ by dataset.
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
The provider model card explicitly identifies proprietary model weights or a proprietary fine-tuned derivative. Current language routes may use newer unnamed checkpoints; catalog family labels are not invented API model IDs.
