---
title: "Async Voice API free inference"
description: "$0.1 for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Async Voice API."
canonical_url: "https://freeinferencing.com/provider/async_voice_api/"
md_url: "https://freeinferencing.com/provider/async_voice_api.md"
last_updated: "2026-09-19"
---

# Async Voice API

> $0.1 for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Current trial
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** $0.10 once
- **API endpoint:** `https://api.async.com`

## Models mentioned

- `async_pro_v1.0`
- `async_flash_v1.5`
- `async_flash_v1.0`
- `async_asr_v1.0`

## Limits and terms

```yaml
signup_credit_usd: 0.1
recurrence: false
expiry: not_published
concurrent_requests: 1
advertised_approximate_free_minutes: 10
minimum_wallet_top_up_usd: 1
```

## What happens to your prompts?

**Not private.** Standard terms grant broad R&D and improvement rights over Input and Output; training requires an email opt-out and cloned-voice recordings may be retained indefinitely until deletion.

Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data.

## Data governance and agreements

```yaml
data_governance:
  review_status: reviewed
  plan_scope: Async Voice API TTS, STT, and voice cloning under standard
    self-service terms.
  prompt_retention: Input content can be hosted and processed under a worldwide
    license for service provision, research, development, and improvement.
  response_retention: Output is user-owned but falls within the broad service R&D
    and improvement license.
  ordinary_logging: Account, device, request, usage, security, and billing data
    are retained for service operation.
  model_training: Default terms permit research and development use; a user must
    email to exercise the documented training opt-out.
  product_improvement: Input and Output can be used to develop and improve Async services.
  human_or_operator_access: Staff and providers may access content for service,
    moderation, support, security, and improvement.
  subprocessors_and_routing: Third-party licensors, service providers, and hosting
    infrastructure may process content.
  deletion_controls: Account termination deletes account content, and users may
    request takedown; recordings used to create cloned voices may otherwise
    persist indefinitely until deletion.
  caveat: Voice-cloning source recordings create a particularly durable retention
    exception.
agreements:
  terms_of_service: https://async.com/terms
  privacy_policy: https://async.com/privacy
```

## Eligibility

```yaml
account_required: true
payment_method_required: false
```

## API compatibility and modalities

- **Compatibility:** Async Rest And Websocket
- **Modalities:** Text To Speech, Speech To Text, Voice Cloning, Speech / audio


## Before you build with Async Voice API

### Read the classification narrowly

This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “One-time trial” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below.

### Resolve the live model route

The snapshot records 4 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online.

### Match the quota to the workload shape

Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms.

### Preserve billing and privacy boundaries

The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Not private** because Standard terms grant broad R&D and improvement rights over Input and Output; training requires an email opt-out and cloned-voice recordings may be retained indefinitely until deletion. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content.

### Follow the evidence, then re-check it

This record links 5 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term.

### Plan fallback without policy drift

A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable.

### Monitor the offer as a dependency

Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity.

### Test one complete request before scaling

Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement.

## Primary sources

- [Voice API pricing](https://async.com/async-voice-api/pricing): Official Pricing
- [Async Voice API](https://async.com/async-voice-api): Official Product
- [Voice API documentation](https://docs.async.com/): Official Docs
- [Terms](https://async.com/terms): Official Terms
- [Privacy](https://async.com/privacy): Official Privacy

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.