Exact audio response contract not published in the reviewed text-only Guard OpenAPI schema.
Generation controls
Each audio request is assessed independently without conversation history. Early-access coverage is prompt attacks only; moderation, PII and custom guardrails remain text-only.Source for Generation controls (opens in a new tab)
Acoustic attack check first; flagged clips stop before transcription. Passing clips are transcribed and screened with the same prompt-attack model and sensitivity levels as text.Source for Architecture (opens in a new tab)
No request model selector established. Policies select detectors; dev_info.model_version is response build metadata.
Access
Early access through provider onboarding; exact API route and size limits not publicly established.
Regions
Confirmed during onboarding
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Processing region and log storage are independent. Log storage defaults to EU and is fixed when the organization is created. The PII guide says detected PII is masked before logging and models are not trained on PII; this does not establish zero retention or a universal no-training promise for all content. Exact retention and enterprise contractual terms remain unverified.
No request model selector established. Policies select detectors; dev_info.model_version is response build metadata.
Access
Enterprise license and container registry credentials. Audio pipeline includes local transcription; exact deployment revision not established.
Regions
Customer infrastructure
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Self-hosted audio processing, including transcription, stays inside customer infrastructure. Local retention and logging depend on deployment configuration; no automatic deletion period inferred.
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.
AI Guardrails Audio SaaS
Not verified
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
How it works
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Minimum reusable input
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Lifetime & refresh
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
How to enable it
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Usage fields
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Billing rules
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Limits & data boundaries
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 15 Oct 2026
AI Guardrails Audio self-hosted
Not verified
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
How it works
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Minimum reusable input
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Lifetime & refresh
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
How to enable it
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Usage fields
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Billing rules
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
Limits & data boundaries
Not collected
No documented model-specific prompt-cache mechanism or tariff established. Client HTTP caching is not inference caching.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 15 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
Managed security component supplied through the provider service and enterprise-licensed private container distribution. No independently trained base checkpoint asserted.
