Catalog

Ask for the field and AIsa finds the source

Products, shops, accounts and posts in one schema, across marketplaces and social platforms, with every value traced to its source. Or call any of 6,157 APIs from 552 providers directly, on the same key.

APIs
6,157
Models
110
Connectors
1,712
Browse by

Live6,157 APIs from 552 providers, passed through with each provider's own fields. Use them when you need the raw response; use unified entities when you want sources you can swap. Polymarket (5), Open-Meteo (11), Brave (2), and Duffel (2) are grouped.

What's the difference?
Browse the catalog

How the catalog works

Two ways to call, one key

The difference is what happens when the provider behind a call changes. With Unified your code stays the same; with Direct you rewrite the call.

UnifiedSoon · Amazon, TikTok Shop and X first

Ask for the field

AIsa defines the entities and fields, picks the source behind every call and can swap it. Every value says where it came from and how it was counted.

social.accounts.get
{ "platform": "x", "handle": "acme_robotics" }

→ Account, the same shape on TikTok or Douyin
DirectLive · 6,157 APIs from 552 providers

Call the provider

Each provider's own APIs and fields, passed through with one key and one bill. You choose the provider and get exactly what it returns.

GET /apis/v1/tikhub/twitter/web/fetch_user_profile
    ?screen_name=acme_robotics

→ TikHub's own JSON
You get
AIsa's entities and fields, each value with its source, time and method
The provider's fields, as the provider sends them
Who picks the source
AIsa, by the kind of field; switchable at any time
You, in every call
Quality
Sources calibrated in public; nothing back, nothing billed
Whatever the provider delivers
Billed
By result, or per query for estimates
Per call, at the provider's price plus a published fee
If the provider changes
Your code doesn't change
You rewrite the call
Unified

Four ways a field gets answered

How AIsa asks, what comes back and what you pay all follow from which kind of field it is.

Verifiable

A creator's email, the company behind a shop, a trademark's status.

Asked
One source at a time, until an answer passes a check
You get
One value and how it was checked
Billed
Only once it passes

Observable

Price, rating, review count, best-seller rank, TikTok Shop sold count.

Asked
A fresh snapshot if there is one, otherwise a live read, otherwise the next source
You get
The value and when it was read
Billed
Only when it comes back

Estimated

Units sold, GMV, search volume, a creator's sales.

Asked
One estimator by default, or two to three side by side
You get
Every figure with how it was counted; median and range on request
Billed
Per query, one source or several

Lists and risk

Best-seller lists, product and creator finders, patent and TRO checks.

Asked
Several sources, pooled and de-duplicated; one risk hit is enough to flag
You get
One list, each row naming its source
Billed
Per row returned
Unified

Every value comes with its provenance

Where it came from, when it was read, how it was counted, and whether it was seen, reported or estimated. The provider's raw fields stay available too, so nothing is lost on the way into the schema.

$39.99
Observed. Read off the public page, like a price or Amazon's “1K+ bought in past month”.
1,204 rep
Reported. Given by the platform to an owner who connected the account, like a seller's own sales.
≈ 1,180
Estimated. A third party's model, like monthly sales or GMV. Always shown with ≈, never called the true number.
One estimate, as it comes backExample
{
  "listing": "amazon:US:B0DEMO1234",
  "units_sold_30d": {
    "value": 1180,
    "value_type": "estimated",
    "source": "jungle_scout",
    "metric": "units.ordered.rolling_30d",
    "collected_at": "2026-10-02T06:10:00Z",
    "confidence": "[from calibration]",
    "resale": "[per source contract]",
    "raw": { "...": "vendor fields, unchanged" }
  }
}

The calibration report

How far each sales estimator runs from Amazon's and TikTok Shop's own signals, by marketplace and category. Published in the open. First edition in preparation.

Get the first edition

A platform we don't cover yet

Tell us where it should reach and what it should do there. The cards marked Soon are already in the queue.

Suggest a platform

If you sell commerce or social data

Map your fields into the schema once and every connected agent can ask for them. The calibration report shows where your numbers hold up best.

Partner with AIsa

Search the catalog

Platforms, unified entities, providers, APIs and connectors.