Skip to main content
AIsa uses a usage-based billing system. Charges are applied based on the type of API you use. There are two pricing categories:
  1. AI Model (LLM) Pricing: billed per token
  2. Data API Pricing: fixed per request for many APIs; some providers use a credit formula based on request dimensions or returned rows
This page provides a high-level overview of both models and links to their detailed pricing pages.

​
1. AI Model (LLM) Pricing

AI model APIs are billed based on token usage. The Models catalog lists every available model with its input and output price side by side, so you can compare rates before you pick one. Each request is charged separately for:
  • Input tokens (prompt tokens)
  • Output tokens (generated tokens)
Prices are defined per 1 million tokens (1M tokens), and input and output tokens are billed independently. This pricing model applies to:
  • Chat completions
  • Text generation
  • Vision-enabled models
  • Tool-enabled models
  • Streaming responses
For the full model pricing table and detailed billing explanation, see AI Model Pricing

​
2. Data API Pricing

Many non-LLM APIs use a fixed per-request billing model. Some data providers have a variable credit-based model instead. For fixed-price APIs, each API page lists its endpoints with the price attached to each one — in the Twitter example above, /apis/v1/twitter/user/last_tweets is billed at $0.0036 per call while /apis/v1/twitter/user/followers is billed at $0.036 per call. For those APIs, each successful request to an endpoint incurs a predefined charge, regardless of response size. This pricing model applies to APIs such as:
  • Search APIs
  • Financial APIs
  • YouTube APIs
  • Scholar APIs
  • Twitter APIs
  • Other structured data and retrieval services
For endpoint-level pricing details and billing behavior, see Per-Call API Pricing. Some paid data APIs, including SimilarWeb, use a credit formula rather than a fixed per-call price. Read the matching endpoint documentation and pricing declaration before a paid request; if a maximum is not documented, do not execute it under the approval-first contract.

​
Choosing the Correct Pricing Model

If your API request:
  • Uses a language model to generate text → Token-based pricing applies
  • Retrieves structured data or performs a search → Read that API’s pricing model; it may be fixed per call or formula-based.
The Models catalog shows per-token prices. Fixed-price API pages show per-call prices; formula-priced APIs publish their formula and cost controls with the endpoint documentation.

​
Usage Tracking and Transparency

All API activity, whether token-based or per-call, is recorded in:
  • Usage Logs
  • Account billing summaries
You can review:
  • Tokens consumed (for AI models)
  • Number of requests (for per-call APIs)
  • Final cost per request
  • Applied pricing rules or group ratios
Charges are deducted from your account balance based on the applicable pricing model.

​
Additional Notes

  • Pricing is usage-based; no fixed monthly platform fees.
  • Pricing may vary by model, provider, group, or endpoint.
  • Always refer to the Models catalog and API pages for the most up-to-date rates.
  • Detailed billing breakdowns are available in Usage Logs.