AIsa

• Name: AIsa
• URL: https://aisa.one/
• Category: agent API gateway / x402 pay-per-call wrapper / multi-API bundle
• Tags: ethereum-ecosystem
• Summary: AIsa is a large agent API menu with x402 attached. The interesting part is the gateway packaging, not the fact that it sells one more pile of models and data feeds behind one endpoint.
• What it does:
  • Exposes a unified API surface for chat models, video generation, search, finance, Twitter/X data, prediction-market data, and CoinGecko-powered crypto data
  • Publishes a docs-wide llms.txt index and multiple first-party “agent skills” that teach coding agents how to use AIsa endpoints for specific tasks
  • Supports API-key access through https://api.aisa.one and a separate x402 pay-per-call flow for AIsa endpoints without requiring a traditional API key
  • Routes x402 payments through Circle Gateway and documents support for 11 accepted EVM mainnets including Base, Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Unichain, Sonic, World Chain, Sei, and HyperEVM
  • Maintains a public GitHub org with docs, a CLI, agent skills, and the nanopayment-x402 reference implementation
  • Packages endpoint catalogs, setup tooling, and wallet-descriptor guidance for autonomous agents that need to fund and consume paid APIs programmatically
• Key claims:
  • The docs-wide llms.txt file describes AIsa as a unified API gateway for autonomous agents with many models, data APIs, and stablecoin payments behind one endpoint
  • The API reference says AIsa exposes a unified API surface at https://api.aisa.one, with OpenAI-compatible chat under /v1 and other APIs under /apis/v1
  • The same API reference organizes the product around chat, video, search, Perplexity, financial, Twitter, scholar, and prediction-market APIs, which makes it a broad gateway rather than a niche vertical API
  • The nanopayment-x402 README says agents can access AIsa endpoints with no API key by paying per call over x402 with USDC through Circle Gateway
  • That README also documents more than 100 priced endpoints across several categories, reinforcing that AIsa is monetizing a large packaged service surface rather than a single product
  • The public GitHub org plus the docs, CLI, agent skills, and example repos make it look like operational packaging for agent builders, not just a marketing shell
• Whitepaper: No canonical standalone AIsa whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the docs-wide llms.txt index, the API reference, the public GitHub organization, and the official nanopayment-x402 repository README; see ../whitepapers/aisa-primary-sources-2026-05-03.md.
• Sources:
  • https://aisa.one/
  • https://aisa.one/docs/llms.txt
  • https://aisa.one/docs/api-reference
  • https://github.com/AIsa-team
  • https://github.com/AIsa-team/nanopayment-x402

Internal linkages

• Protocol base: x402
• Stronger directory reference: 402-index

Control surface

• The leverage sits in gateway admission, endpoint packaging, API-key versus x402 access defaults, and which upstream models or data vendors get bundled behind one paid surface.

• That makes AIsa a gateway operator with a payment wrapper, not a new protocol family.

• Read it upward toward stronger paid-request standards and machine-payments rails, not sideways toward every other API bundle.

• Last reviewed: 2026-06-03 UTC