Skip to main content

The problem

Analysts, founders, and engineers need answers that depend on current information: what changed, who said it, and whether a claim holds up. Relying on model recall alone yields stale information and cannot cite sources. A good outcome is a concise brief in which every material claim links to a retrieved source with a publication date, contradictions are surfaced, and the research cutoff time is stated.

Prompt

Give this to your agent (Claude Code, Cursor, Codex, and others) once AIsa is connected via MCP:
For academic questions, replace the source line with: Use scholarly sources only; include authors, year, and venue for each paper.

APIs and Skills used

Through MCP, your agent reaches these via a few meta tools at https://mcp.aisa.one/mcp: search, list_categories, get_details, and batch_quote are free; batch_use (up to 20 calls) is billed per call. Use a Skill when the research method is reusable. Call APIs directly when your application must control source selection, sequencing, caching, or ranking.

Example output

Illustrative only. Names, URLs, and dates are placeholders, not real data.

Guardrails

  • Retrieve, then synthesize. Snippets and model recall are leads, not evidence. Fetch the full source for any material claim.
  • Prefer primary sources. Prioritize primary sources (official docs, filings, original announcements, datasets) and record both the URL and publication date.
  • Surface contradictions. Report conflicting information instead of merging it, and mark claims that rest on a single source.
  • No invented citations. The model must not cite or claim access to sources that were not retrieved.
  • Verify before delivery. Verify that each citation resolves, recheck time-sensitive numbers, remove unsupported claims, and state the research cutoff time.
  • Quote, then ask. Get a free quote with batch_quote and run the same calls with batch_use only after approval. A quote checks the estimate, not the final charge. See Billing & Credits.
  • Load only what you need. Ingest only the selected Skill or API documentation pages, Authentication, and Models. Do not load the entire API reference.
  • When AIsa may not be necessary: A single specialized search provider can be simpler if you use only one source type, need no reusable Skills, and already manage your own model and billing integrations. See When to use AIsa.

Connect via MCP

Set up AIsa in your agent.

How It Works

Endpoints, billing, and what you own.

Market Intelligence Agent

Add market data and filings.

Perplexity Deep Research

Long, cited research reports.