Skip to content Docs index for AI agents (llms.txt)

Start herePlans

Plans

Pay as you go, Pro, and Enterprise.

Updated 2 min read

Token Streamer has three plans: Pay as you go, Pro, and Enterprise. Each organization has one plan.

Pay as you go

You buy credits in advance and spend them on model usage. A one-time purchase adds credits and does not start Pro. You can also use your own provider keys. Usage metadata has its own retention setting. Request text is not stored unless an owner opts in, for 1 to 7 days at most.

Pro

Pro is a recurring subscription alongside model usage. Pro organizations never retain request text (see zero data retention below). Usage and operational metadata remain available. See Pro subscriptions for how it works.

Enterprise

Enterprise is a contact-us agreement for a deployment you own. Contact the Benavi team to agree the infrastructure, support, and commercial scope. You control your application database, credential encryption, runtime, storage, and network configuration. Choosing an inference region alone does not mean all infrastructure runs in that region.

Zero data retention

Pro and Enterprise include zero data retention: Token Streamer does not store the text of requests or responses.

  • Pro is always zero data retention. Text capture cannot be turned on.
  • Enterprise starts with zero data retention. The organization owner can opt in to text capture for up to 90 days on the Data controls page. While capture is on, the organization is not zero data retention.
  • Usage metadata (model, token counts, timing, cost) is still kept for billing and reports, under its own retention setting. It never contains request or response text.
  • Zero data retention covers Token Streamer only. Your AI provider's own retention depends on your provider account, or on Token Streamer's provider agreements for credit-funded calls.

The Data controls page shows a Zero data retention notice when it applies.

Moving to Pro or Enterprise turns off text capture and deletes retained request text. Usage metadata stays under its own retention rules. Deletion does not cover separately retained infrastructure backups.