Skip to main content

​
What is AIsa?

AIsa is the resource and payment layer for AI agents: one account and one balance to discover, call, and pay for live LLM and media models and 100+ data APIs - search, finance, social, SEO, sales, and more. See How It Works.

​
How is AIsa different from an LLM gateway?

An LLM gateway puts several models behind one API. AIsa does that, and adds the data APIs agents act on, an MCP server and Skills so agents can find and call them, and per-call billing with spend caps so agents can pay for what they use. If your workload only needs one model provider, a direct integration can be simpler; AIsa helps once an agent needs several providers.

​
Which way should I connect?

​
Do I need to change my OpenAI or Anthropic code?

No. Change the base URL and the key: https://api.aisa.one/v1 for the OpenAI SDK, https://api.aisa.one for the Anthropic SDK. Standard parameters and streaming work as before. See OpenAI / Anthropic SDK.

​
What tools does the MCP server expose?

A small set of meta tools: search and list_categories to find an operation, get_details (also served as batch_get_schema) for its full contract, batch_quote to price the exact calls without running them, and batch_use to run up to 20 calls at once. All but batch_use are free; batch_use is billed per call. use remains as a deprecated single-call form. Your agent reaches the whole data catalog through these tools instead of loading hundreds.

​
Should my agent use a Skill or call APIs directly?

Use a Skill when an existing one already covers the outcome - it encodes which tools to call, in what order, and how to present the result. Call APIs directly (over HTTP or MCP batch_use) when your application needs its own sequencing, retries, or data processing. You can combine both: a Skill for the common path, direct calls for the rest.

​
How is usage billed?

Models are billed per token; data APIs per request, either a fixed rate per call or metered from what the request returns. Everything draws on one prepaid balance, and discovery - docs, /v1/models, MCP search, get_details, and batch_quote - is free. The docs explain billing rules but do not list prices; see aisa.one/models and aisa.one/api, and Billing & Credits for quotes and spend caps.

​
Can I cap what an agent spends?

Yes. Give each agent its own API key with a spending limit in the Console. That limit is the hard ceiling on what the key can spend. For a single call, endpoints that declare maximum-price support accept X-AISA-Max-Price-USD over HTTP: if the cost estimate exceeds your maximum, the gateway rejects the request with 402 before calling the provider. Over MCP, price the exact calls with batch_quote first and run them with batch_use only when the quote fits your budget. Both check the estimate; neither caps the final charge. Model routes such as /v1/chat/completions do not apply this header, so bound their cost with max_tokens and the key’s spending limit. See Billing & Credits.

​
Does every endpoint support machine payments (MPP or x402)?

No. AIsa supports the Machine Payments Protocol (MPP), not x402, and only on selected read-only data endpoints. The live list is the discovery document at https://api.aisa.one/openapi.json; everything else needs an API key. See Machine Payments.

​
Which models are available?

GPT, Claude, Gemini, Grok, DeepSeek, Qwen and Wan, Kimi, MiniMax, GLM, ByteDance Seed and Seedream, Hunyuan, MiMo, and more, plus embedding, image, and video models. The catalog changes often: GET https://api.aisa.one/v1/models and aisa.one/models are always current, and the model catalog lists IDs and routes.

​
Does AIsa store my prompts or outputs?

No. Request content is processed transiently and discarded; AIsa keeps only operational metadata such as timestamps, key identifiers, token counts, cost, and status. See Security & Privacy.

​
How do I get started?

Follow API Key & First Call for code, or Connect via MCP for an agent.