Product data from eleven marketplaces, in one schema
Direct endpoints for Amazon, TikTok Shop, and eBay work on your key today, and Unified calls for all eleven are coming soon.
One question gets the same fields from every marketplace
Listing, Shop and Creator come back in one schema, each value with its source, method and time.
11 marketplaces
Example · fictional brand Acme
Direct endpoints you can call today
Each marketplace's own endpoints, on your AIsa key and priced per call.
Billed only for answers
A verified field bills when it passes and an estimate per query. An empty answer is free.
Unified entities
Planned Unified calls
Contract fields
Direct endpoints today
Four kinds of fields, each answered its own way
A price can be read live, while a sales figure can only be estimated.
Always the latest reading
Price, rating and rank come from a fresh snapshot or a live read, stamped with the time.
Billed when it comes back
Estimates side by side
Sales and GMV come from two or three estimators at once, each with its method and the range.
Billed per query
Checked until it verifies
Creator emails and the company behind a shop. Sources are tried in turn until one verifies.
Billed once it passes
Lists merged, risks flagged
Rankings and searches come back de-duplicated. One patent, trademark or TRO hit is enough to flag.
Billed per row
14 entities answer what an agent asks about a product
All of them are Unified and coming soon. Each opens its catalog page.
Product
The same item across marketplaces, matched by GTIN, brand and model, image and title.
9 draft fields
LiveStream
One shoppable live session: the creator, the products on sale and what it sold.
Fields pending · 4 calls
All commerce entities
Fields, sources and planned calls for each one, in the catalog.
What each of the eleven marketplaces has today
Direct endpoints work now, while Unified calls and sales estimates are planned.
Patents, trademarks and TRO cases are checked on all eleven. Estimator counts follow the phase-one source plan.
Fields stay fixed once they ship
Once your agent relies on a field, it stays put.
- Platform IDs kept as issued
- An ASIN stays an ASIN. Listings and shops are keyed by marketplace and platform ID.
- IDs that never change
- AIsa IDs are never changed or reused, even when records merge or split.
- Linked with a confidence score
- The same product on two marketplaces is linked with its evidence. Weak matches are left out.
- Every value labeled
- Source, collection time, method, and whether it was reported, observed or estimated.
- Methods kept apart
- Two tools that count GMV differently give two metrics, never one blended number.
- Published calibration
- How far each source's estimates run, by marketplace and category.
Connect your agent to the resource layer
Connect over MCP in minutes. One schema covers every platform, and you pay only for results.