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 49 vendor APIs directly, on the same key.

APIs
5,000+
Models
105
Connectors
1,686
Browse by
UnifiedAIsa's entities and fields, sources swappableDirectvendor endpoints, as the vendor sends themWhat's the difference?
Browse the catalog

Commerce12

One Listing for every marketplace: fresh prices, sales estimates side by side, and the shop and company behind it.

  • WalmartSoon
  • ShopeeSoon
  • EtsySoon
  • Mercado LibreSoon
  • OzonSoon
  • ShopifySoon
  • 1688Soon
  • IP & TRO checksSoon

Social24

Read accounts and posts on 20 platforms. Publish, schedule and reply through accounts you connect: live on X, soon on 12 more.

Results from seven search engines, plus keyword, backlink and traffic data for any domain from DataForSEO, Semrush, Similarweb and Ahrefs. Publishing to WordPress and Wix is coming.

Ratings & app stores5

Store listings, ratings and traveler reviews.

Company & people5

Firmographics, decision-makers and registry lookups, for outbound and due diligence.

  • HubSpotSoon

Ads & creators16

Ad libraries, top ads, creator marketplaces and trend indexes. Campaign management on eight ad platforms is coming.

Market data3

Fundamentals, crypto prices and prediction-market order books.

Public data3

Economic series, weather and official filings.

Research & web4

Search, crawl and deep-research APIs for agents that read before they act.

Agent tools11

Tools your agent uses directly: an inbox of its own and flight and hotel booking. Phone numbers, SMS and messaging apps are coming.

  • iMessageSoon
  • RCSSoon
  • SMSSoon
  • Phone numbersSoon
  • Voice callsSoon
  • DiscordSoon
  • SlackSoon

How the catalog works

Two ways to call, one key

The difference is what happens when the vendor 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 · 50 APIs, 1,949 endpoints

Call the vendor

Each vendor's own endpoints and fields, passed through with one key and one bill. You choose the vendor 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 vendor's fields, as the vendor 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 vendor delivers
Billed
By result, or per query for estimates
Per call, at the vendor's price plus a published fee
If the vendor 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 vendor'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, vendor APIs, endpoints and connectors.