What happens to my code when you change a data source?

Nothing. Your agent calls AIsa's fields; which source sits behind each one is our call and can change without touching your code.

Can I still get a vendor's original fields?

Yes. Shared fields cover what is comparable across platforms, platform-only fields keep a platform prefix, and each source's raw response stays available for deeper analysis.

How do I tell an estimate from a reported number?

Every value carries a type — reported by the platform, observed on the page, or estimated by a model — plus its source, method and collection time. Estimates also come with a range.

Per result. Verifiable fields are billed when verification passes, observed fields when they come back, and estimates per query in a single- or multi-source tier. Empty results are free.

Can my agent pay on its own?

Yes. Agents running unattended can pay per call with x402 — no account or monthly plan required.

Is the 5,000+ API catalog still available?

Yes, with the same key and billing. Catalog APIs keep each upstream's original parameters and fields.

Stop writing a new integration for every platform

Your agent asks for what it needs and gets the same fields back on twenty platforms, each value with its source and collection time.

Connect your agent Read the docs

20 platforms

One schema across 11 marketplaces and 9 social platforms.

5,000+ APIs

Same key for the full catalog, models and skills.

Works with the agent you already use

Connect your agent

Claude Code
Cursor
Codex
ChatGPT
Hermes
OpenClaw
Manus

Data your agent can cite, writes it can retry

The two things that break agents in production: numbers nobody can trace, and actions that run twice.

Numbers your agent can cite

Each value arrives with its source, method and collection time, and says whether the platform reported it, the page showed it or a model estimated it.

Writes that are safe to retry

Every write takes an idempotency key, so a timeout never posts twice. Each target gets its own status, link and error.

A contract your code can rely on

Once a field ships, your code depends on it. These rules hold when we switch sources or ship a new version.

Versioned, never rewritten: A field's meaning is fixed once it ships. Changes come as a new version, and the old one keeps working through a transition period.
IDs that stay put: Platform IDs are kept exactly as the platform issues them. AIsa IDs are never changed or reused.
Nothing lost in translation: Platform-only data keeps a platform prefix, and each source's raw fields stay available when you need them.
Every error has an owner: Each error says whether your request, the platform or AIsa has to act, and whether a retry will help. Upstream error text never leaks through.
Ask before you post: What each platform allows — formats, limits, edits, DMs — is queryable. Prechecks that fail are free.
Webhooks for every state change: Published, failed, new comment, authorisation about to expire — pushed to you as it happens.

Field-by-field details live on the product pages: Commerce data and Social.

Built in

For agents that run unattended

Compare sources in one call, reach every platform with one request shape, and pay only for what comes back.

Several sources, one call

Sales and GMV come back from several sources side by side, each with its method, plus a range and how closely they agree.

One request shape

The same call reads a post on X or a listing on Temu. No per-platform parsing in your agent.

Agents that pay their own way

Empty results, failed prechecks and unsent posts cost nothing. Agents running unattended can pay per call with x402 — no account to open.

FAQs

For teams building on AIsa

Can't find what you're looking for? Talk to us.

Schema

Billing and access