# API usage and billing preview

Source: https://iachecker.com/docs/api-usage-and-billing
Status: Design preview
Last verified: 2026-08-08

The web product uses input-word credits for eligible writing operations. Public API metering is not launched and will require a versioned billable-unit definition before customers can rely on it.

## Today's word-credit model

The existing web-product calculation is based on whitespace-delimited input words and a tool multiplier. It does not expose provider prompt tokens or completion tokens as the customer billing unit.

**Existing web-product unit**

```text
word_credits = ceil(input_words × multiplier)
```

## Requirements for public API units

- A versioned counting algorithm
- Defined behavior for Chinese, Japanese and other non-space-delimited languages
- Separate units for synchronous text, file extraction and compute-heavy media jobs
- Usage fields returned with every billable response
- Account-level usage exports and predictable reset periods

## No token contract yet

> **Do not build against an inferred price**
>
> Token pricing, media job units, API quotas and overage behavior are not published. The eventual API reference and pricing page will be the source of truth.

## Documentation index

- [IA Checker documentation](https://iachecker.com/docs)
- [Assistant index](https://iachecker.com/llms.txt)
- [Privacy Policy](https://iachecker.com/privacy)