Skip to main content
GET
Reference example
Domains competing with a target in Google organic search. Billing is per returned data row (up to 20 rows). Current prices are on aisa.one/api. A broad seed returns more rows, so the input size decides the cost — start narrow. ⚠️ The response is semicolon-delimited text, not JSON — parse it as CSV-style rows. Related: get_semrush-domain-vs-domain.
First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. Your agent then reaches every endpoint through five tools: search, list_categories and get_details are free, use and batch_use are billed per call. Setup per client is in Connect via MCP; the live tool list and what each call costs are on aisa.one/mcp.
Set this endpoint up in your agent →

Cost and request rules

Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.08
  • Cost contract: response_count
  • Published reference multiplier: 1.0
  • Declared maximum count/units: 20
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

database
string
required
domain
string
required

Response

Semicolon-delimited rows. Header: Domain;Competitor Relevance;Common Keywords;Organic Keywords.

The response is of type string.