The unified resource and transaction network for AI agents.
AIsa gives agents and developers one programmable interface to discover, access, and pay for AI models, APIs, real-time data, SaaS tools, and other digital services.
Website | Documentation | Console | API Reference
Most digital services are still designed for people: each provider has its own account, credential, contract, billing model, and integration. That structure does not scale well for agents that need to discover capabilities and use them at runtime.
AIsa brings the resource and transaction sides together:
- Discover: inspect models, APIs, Skills, and machine-readable capability manifests.
- Access: use supported resources through a common AIsa credential and standard interfaces.
- Transact: meter usage and pay per use through account billing or supported machine-payment flows.
- Operate: review usage, apply spending controls, and add capabilities without rebuilding every provider integration.
The model gateway is one AIsa capability, not the whole product. AIsa also connects agents to live data, search, software tools, reusable Skills, and payment-enabled services.
| Goal | Start here |
|---|---|
| Make a first request | Getting Started |
| Connect an existing agent | Agent Quickstart |
| Choose a capability by outcome | Capabilities by Goal |
| Choose between models, Skills, and direct APIs | Capabilities by Interface |
| Evaluate product fit and trade-offs | When to Use AIsa |
| Browse every endpoint | API Reference |
| Understand the broader architecture | Agent Capability Layer |
| Read the Chinese documentation | AIsa Chinese Documentation |
| Path | Purpose |
|---|---|
guides/ |
Setup, authentication, pricing, dashboard, and tutorials |
concepts/ |
Product and architecture concepts |
evaluate/ |
Fit, security, pricing, and capability evaluation |
use-cases/ |
Outcome-oriented implementation guides |
agent-skills/ |
Reusable agent Skill documentation |
api-reference/ |
Endpoint-level API documentation |
openapi/ |
Source OpenAPI specifications by provider or capability |
zh/ |
Chinese documentation |
docs.json |
Mintlify navigation, theme, and site configuration |
The site is built with Mintlify. With Node.js 20.17 or newer, run:
npx mint devThe preview is available at http://localhost:3000 by default.
When changing an OpenAPI source, regenerate a local consolidated spec:
python3 -m pip install pyyaml
python3 scripts/consolidate_openapi.py --output /tmp/aisa-openapi.yamlopenapi/*.json files are the source of truth. The root openapi.yaml is
generated by the sync workflow and should not be edited directly.
After the generated openapi.yaml commit is pushed to main, the workflow
sends a docs_openapi_updated repository dispatch to
AIsa-team/aisa-tool-router. Its payload contains the immutable docs commit,
the consolidated spec SHA-256, the source commit/ref, and the workflow run ID.
The workflow uses the installed AIsa-team/aisa-release-bot GitHub App to mint
a short-lived installation token scoped to the private Tool Router repo. The
docs repository must define TOOL_ROUTER_DISPATCH_APP_ID as an Actions
variable and store the App PEM in the
TOOL_ROUTER_DISPATCH_APP_PRIVATE_KEY Actions secret.
Dispatch runs in a sibling job after the docs revision is captured. Its
always() guard lets Tool Router delivery proceed when a later notification
step fails, while a delivery failure cannot roll back the published docs
revision.
If delivery must be retried after the generated file is already current, run
the workflow manually from main with dispatch_tool_router enabled.
- Lead with the task a developer or agent is trying to complete.
- Distinguish models, Skills, direct APIs, and payment surfaces precisely.
- Document current behavior, authentication, cost, and failure modes without implying unsupported guarantees.
- Keep English pages and their
zh/counterparts aligned when both exist. - Never commit real API keys, account data, or production response payloads.
This repository is available under the MIT License.