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
Catalog
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.
One Listing for every marketplace: fresh prices, sales estimates side by side, and the shop and company behind it.
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.
Store listings, ratings and traveler reviews.
Firmographics, decision-makers and registry lookups, for outbound and due diligence.
Ad libraries, top ads, creator marketplaces and trend indexes. Campaign management on eight ad platforms is coming.
Fundamentals, crypto prices and prediction-market order books.
Economic series, weather and official filings.
Search, crawl and deep-research APIs for agents that read before they act.
Tools your agent uses directly: an inbox of its own and flight and hotel booking. Phone numbers, SMS and messaging apps are coming.
How the catalog works
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.
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 DouyinEach 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 JSONHow AIsa asks, what comes back and what you pay all follow from which kind of field it is.
A creator's email, the company behind a shop, a trademark's status.
Price, rating, review count, best-seller rank, TikTok Shop sold count.
Units sold, GMV, search volume, a creator's sales.
Best-seller lists, product and creator finders, patent and TRO checks.
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.
{
"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" }
}
}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 editionTell us where it should reach and what it should do there. The cards marked Soon are already in the queue.
Suggest a platformMap 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 AIsaPlatforms, unified entities, vendor APIs, endpoints and connectors.