Token-based licensing for the Prisma AIRS Runtime API is a consumption model that shifts from fixed API calls to token consumption, where usage is priced per billion monthly tokens. This model aligns with industry standards for AI applications, providing a more granular, content-driven metric for measuring your Prisma AIRS Runtime API usage.

For context, one token is equal to four characters. This licensing is based on billions of tokens per month. At the end of each calendar month, your token quota resets. Whenever you send a prompt, model response, or tool call to the Prisma AIRS Runtime API, the system counts the number of tokens and subtracts it from your monthly quota.

This licensing model fundamentally changes how you measure consumption. The new model measures consumption based on the volume of "tokens" processed from your scan content. You now define Monthly Tokens (Billions) in your Prisma AIRS Runtime API deployment profile. For each Prisma AIRS Runtime API deployment profile, enter the number of tokens (billions) that you expect to consume per deployment profile per month.

The token-based licensing architecture involves several key components that interact to manage your API usage:

• Prisma AIRS API—This is the primary service endpoint that receives your scan requests and initiates the token computation process from your scan content.
• Customer Support Portal (CSP)—You use this interface to define and manage your token-based deployment profiles, specifying your allocated monthly tokens.
• Strata Cloud Manager (SCM)—This management platform allows you to activate subscriptions, associate deployment profiles with your tenants, generate API keys, and monitor your token consumption through dashboards.

The token lifecycle begins when you define your deployment profile in the Customer Support Portal (CSP). You specify your desired Monthly Tokens (Billions) in the CSP to establish the licensed capacity for your Prisma AIRS Runtime API usage. You then activate your Prisma AIRS API deployment profile by onboarding Prisma AIRS in SCM. You associate the defined deployment profile with a specific Tenant Service Group (TSG) in SCM, either an existing one or a new one. This process activates the token-based subscription by calling a new IT license activate endpoint, which registers the license and enables token-based consumption for your deployment profile.

You generate unique API keys within SCM for your applications. You use these keys to authenticate scan requests to the Prisma AIRS API, and they link to your activated token-based deployment profile. When you submit a scan request to the Prisma AIRS API, the system analyzes the content of the scan and computes the corresponding token count. The system persists the computed token counts for each scan request in a backend database and simultaneously transmits them.