aisa.one valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for aisa.one:
1. POST https://agentwebmap.com/v1/sites/aisa.one/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://aisa.one/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/aisa.one/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/aisa.one).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

AIsa

The resource layer for AI agents: one MCP endpoint and one key for web search, SEO, social, finance, crypto, prediction markets, people and company data, and LLMs.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T19:29:09.765Z. Cached copy · Source on aisa.one

# AIsa

> The resource layer for AI agents: one MCP endpoint and one key for web search, SEO, social, finance, crypto, prediction markets, people and company data, and LLMs.

This is the setup guide for agents. Read it top to bottom; load "Optional" links only when the task needs them.

## 1. Connect

Pick the first option that applies. Run the command yourself; the user only approves the browser sign-in.

### A. Your client supports remote MCP and can open a browser (default)

Add a remote MCP server named `AIsa` with URL `https://mcp.aisa.one/mcp` (Streamable HTTP), using your client's own command or config file. Auth: browser OAuth, no key needed. In a chat app (Claude, ChatGPT), the user adds it as a custom connector in settings.

Adding the server does not always start sign-in. If no sign-in window opens, start it from the client's own MCP authentication entry (a menu, command, or connector button); if only the user can reach that entry, tell them where it is. Sign-in is the slow step, not the API. Before it starts, tell the user in one line that an AIsa sign-in window or card is about to open and to click **Allow** (one click if the browser is already signed in to AIsa). Do not call step 2 until the user says sign-in is done or the AIsa tools appear; calling it earlier only returns 401, so do not retry in a loop.

If the client must restart to load the server, tell the user and wait. If you cannot add the connector yourself (sandbox, permission denied), give the user the server name and URL above and wait. Do not fall back to another method.

### B. Your client supports remote MCP but has no browser (CI, SSH, container)

Same endpoint, with the header `Authorization: Bearer $AISA_API_KEY` set in your client's MCP config instead of browser sign-in.
If `AISA_API_KEY` is not set, ask the user to create a key at https://console.aisa.one/api-keys and set it in the environment; never ask them to paste it into chat. Never print, log, or commit the key.

### C. The client has no MCP support

Use the CLI: `npm install -g @aisa-one/cli && aisa login` (Node.js 18+). Guide: https://aisa.one/docs/get-started/cli.md

### D. Calling AIsa over HTTP from your own code

- LLMs, OpenAI-compatible: `https://api.aisa.one/v1` (Gemini GenerateContent: `https://api.aisa.one/v1beta`)
- Data APIs: `https://api.aisa.one/apis/v1`
- Auth: `Authorization: Bearer $AISA_API_KEY`
- Exact paths and schemas: https://aisa.one/docs/api-reference

## 2. Verify

Make one free authenticated call on the interface you connected:

- MCP (A, B): call `account` (no arguments). If it is not in the tool list, call `use` with `{"operation_id": "account"}` instead. Returns the key, balance, and usage.
- CLI (C): `aisa balance`. (`aisa whoami` is local only and does not count.)
- HTTP (D): `GET https://api.aisa.one/v1/credits/balance` with the Bearer header returns 200 with the balance: a free protected call, the same check `aisa balance` makes. `GET /v1/models` is only a transport check;
…

Related sites

Other listed sites in Marketing. See the whole category →

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=aisa.one · GET /v1/domain/aisa.one · this page as Accept: application/json or text/markdown · MCP lookup_domain