Skip to main content
AIsa uses usage-based billing across model inference and billable API capabilities. Exact prices depend on the selected model, route, or endpoint and can change independently of this evaluation page. Use current pricing sources for final decisions.

​
Sources of truth

Do not copy a price from a comparison or conceptual article into production logic.

​
Estimate the complete workflow

A multi-step agent may incur more than one charge. Estimate:
  1. Retrieval or API calls.
  2. Model input and output tokens.
  3. Retries or fallback routes.
  4. Enrichment calls for shortlisted records.
  5. Media generation or other per-request capabilities.
The cheapest individual endpoint may not produce the lowest complete-task cost if it requires more retries, tokens, or follow-up calls.

​
Budget controls

Define:
  • Maximum cost per API call.
  • Maximum cost per task.
  • Daily or monthly workspace limits.
  • Whether the agent may select a more expensive fallback.
  • Which amount requires confirmation.
  • What happens when the balance is insufficient.
For runtime purchasing, also see Machine payments for agents.

​
Compare alternatives fairly

When comparing AIsa with direct providers or another gateway, include:
  • Model or endpoint price.
  • Engineering work for additional providers.
  • Billing and credential management.
  • Required data APIs or tools.
  • Reliability and fallback requirements.
  • Observability and audit needs.
A direct provider can be the simpler option for a stable, single-provider workload. A shared capability layer may be more useful when the workflow combines several providers or capability types.

​
Verify before production

  • Confirm the exact model ID or endpoint.
  • Check current price units.
  • Run a small representative request.
  • Inspect the usage record.
  • Measure the complete workflow, not only one call.
  • Add budget alerts before scaling traffic.
For the broader product decision, see When to use AIsa.