For the complete documentation index, see llms.txt. This page is also available as Markdown.

Textual billing overview

Textual billing is based on the number of words that it scans to identify sensitive values, called entities.

Billing is per 1,000 words

Textual always bills for every 1,000 scanned words. Textual counts actual words, not tokens. For example, "Hello, my name is John Smith." counts as six words.

Free trial versus pay-as-you-go versus contract accounts

A free trial account is not billed, but is restricted to a specific number of words. After they reach that limit, Textual no longer performs any scans and does not allow the account to add files to datasets.

A pay-as-you-go account does not have a limit. The account credit card is billed each month based on the number of scanned words from the previous month.

A contracted account does not have a limit, but it might have a number of words that it pays for when the contract starts. If the account exceeds that word count before the contract period ends, then they are billed for the additional scanned words.

What counts as a scan?

A scan specifically means that Textual analyzes a piece of text or a file to identify sensitive values.

This includes when:

  • You add a new file to a dataset. Textual immediately scans the file.

  • You change the dataset configuration in a way that requires Textual to scan the files again. For example, you change the activated custom entity types. Textual prompts you when a new scan is required.

  • You use the SDK or API to send redaction requests for individual text strings or files.

  • You add a file to a guided redaction project. Textual scans the file to identify sensitive values to redact.

What does not count as a scan?

Textual does not bill you for the following:

  • Failed scans of a file in a dataset or an SDK request. For example, if Textual is unable to parse a file, then it does not count that file as having been scanned.

  • Failed SDK requests to redact text, JSON, XML, or HTML strings. If the response is not 200, then the text is not considered scanned.

  • New rendering of a dataset output file. For example, when you change the entity type handling or synthesis configuration, Textual does not re-scan the file.

Last updated

Was this helpful?