How AIsa Works

AIsa sits between your agent or application and the upstream model and data providers. You authenticate once, send requests to an AIsa endpoint, and every call is billed against a single shared balance.

​

1. Authenticate

Every credential draws from the same account balance. See Authentication for key management and OAuth details.

​

2. Call an endpoint

Endpoint definitions and parameters follow the OpenAPI specification. Through MCP, an agent uses 5 core tools instead of loading hundreds into its context: search and list_categories to discover tools, get_details to inspect inputs and quotes, and use (or batch_use for up to 20 calls) to execute them.

​

3. Pay per use

• One balance: Models, data APIs, MCP calls, and the CLI all draw from the same prepaid wallet. Top up in Console → Billing.
• Models are billed per token (input, output, and cached tokens when reported by the provider).
• Data APIs are billed per request: either a fixed price per call, or metered by what the request consumes (results, rows, pages, or provider credits).
• Discovery is free: Browsing docs, listing models via /v1/models, and MCP discovery (search, list_categories, get_details) cost nothing. You only pay for executed calls.
• Spend controls: Set a spending limit on each key in the Console; that is the hard ceiling. On endpoints that declare maximum-price support, pass a maximum via X-AISA-Max-Price-USD (or max_price_usd in MCP use): the gateway rejects the call before any provider is called if the estimate is higher. This checks the estimate and does not cap the final charge. Model routes do not apply it; bound them with max_tokens and the key’s limit.

Current rates are published at aisa.one/models and aisa.one/api. For detailed billing rules, see Billing & Credits. Selected endpoints also accept the x402 machine-payment protocol; see Machine payments for agents.

​

What AIsa handles vs. what you own

Treat state-changing operations (creating, updating, deleting data, or spending funds) with extra care: use scoped keys, require explicit user confirmation when needed, and avoid automatic retry loops on failed calls.

​

When to use AIsa

AIsa is ideal when your agent or application needs multiple providers: mixing LLM reasoning with live data, switching between model families, or accessing multiple data sources without managing separate contracts. If your workload only ever uses a single model provider and you already have an existing billing relationship with them, connecting to that provider directly may be simpler.

​

Next steps