What is a “resource layer”, and how is it different from calling the APIs myself?

You ask for an entity — a post, an account, a listing — and get AIsa's schema back. We pick the source behind each field, label every value with where it came from and when, and swap sources without changing what your agent sees.

Which platforms and entities are covered today?

Social: posts, accounts, comments, messages and publishing across X, TikTok, Instagram, Facebook, YouTube, LinkedIn, Pinterest, Threads and Reddit. Commerce: listings, shops, keywords, creators, brands and IP risk across Amazon, TikTok Shop, Temu and more, rolling out through Q4.

How does billing work?

Per result returned. Verified fields are billed only when verification passes; estimates are billed per query, single- or multi-source. Empty responses, failed prechecks and scheduled-but-unsent posts are free.

How do I connect my agent?

Add the AIsa MCP server to Claude Code, Cursor, Codex, ChatGPT or any MCP client, or install the AIsa skills. One key covers the resource layer and the proxy catalog.

Where does the data come from, and is it compliant?

From platform APIs, licensed partner feeds and AIsa's own models and snapshots. We do not bypass platform protections, every value carries its source and collection time, and publishing always runs under the account owner's authorisation.

Can I still call the 5,000+ APIs directly?

Yes. The proxy catalog — 5,000+ APIs, 110+ models and 40+ skills behind one key — stays available alongside the resource layer, with the same key and billing.

Backed by Alibaba · Tribe Capital · Draper Associates · Sumitomo

The resource layer for AI agents

Real-world data your agent can trust. Every entity, every platform, one schema — and you only pay for results.

Connect your agent Explore the schema

AIsa resource layer · PostSample

Same schema onXTikTokInstagramFacebookYouTubeLinkedInPinterestThreadsReddit

AIsa resource layerOne schemaBest source per fieldEvery value labelledPay per result

“Meet the Acme Mini Picker”

Post · TikTok

Field	Value	Source	Method	As of
views	3.8M	Platform API	Plays, lifetime	2026-09-30
likes	212K	Platform API	Public count	2026-09-30
engagement_rate	6.4%	AIsa model	(likes + comments) ÷ views	2026-09-30
mentioned_products	2 products	AIsa model	Detected in caption and video	2026-09-30
author	@acme	Platform API	Public post	2026-09-30
posted_at	2026-09-21	Platform API	Publish time, UTC	2026-09-30

6 fields · 2 sources · one schema● 1 result billed · no result, no charge

Works with the agent you already use

Claude Code

Cursor

CodexChatGPT

Hermes

OpenClaw

Manus

Claude Code

Cursor

CodexChatGPT

Hermes

OpenClaw

Manus

5,000+

APIs behind one key

110+

Models

40+

Skills

250k+

Agent users

The proxy catalog stays available alongside the resource layer.Browse the catalog

What you get

Built for agents that have to be right

Every value your agent gets back is calibrated, labelled and billed only when it exists. The same four promises on every entity and every platform.

Accurate by default

Each field comes from the source that tests most accurate for it, and we publish the calibration. No vendor research on your side.

Every value is traceable

Source, method and collection time ride along with every number, so your agent can cite it and you can audit it.

Every platform, one schema

A post from TikTok or a listing from Temu comes back with the same fields. No per-platform parsing in your agent.

Pay only for results

Billed per result returned. Verified fields are charged only when verification passes; empty responses are free.

Fields only ever get added

Published fields never change meaning. Breaking changes ship as a new version with a transition period.

Reported, observed or estimated

Every value says which kind it is, so estimates are never mistaken for platform-reported numbers.

Licensed sources only

Platform APIs and partner feeds under contract. No bypassing platform protections, ever.

Two lines

Social that acts, commerce that compares

The social line lets your agent read, publish and reply across nine platforms. The commerce line puts listings, shops, keywords and creators from eleven marketplaces side by side.

Reply to comments

Your agent reads every comment under a post and drafts the answer, with approval before anything is sent.

Publish once, everywhere

One request, several target accounts. Each target gets its own status, post link and error — and the same request never posts twice.

One inbox

Comments, DMs and mentions from every platform land as the same entities, so one agent can work them all.

Estimates side by side

Sales and GMV have no single truth. Your agent sees each vendor's number with its method, plus the agreement between them.

Eleven marketplaces, nine social platforms

Amazon, TikTok Shop, Temu, Walmart, Shopee, Ozon, Mercado Libre, Etsy, Shopify, eBay and 1688 — plus X, TikTok, Instagram, Facebook, YouTube, LinkedIn, Pinterest, Threads and Reddit.

Placeholder

We replaced a dozen vendor integrations with one schema. Our agent now cites a source and a date for every number it puts in front of a client.

NameRole, company

How it works

Three steps to the resource layer

No SDK to learn and no contract to sign. Your agent talks to one MCP server and gets one schema back.

KEY

aisa_sk_…

Get a key

Create a free key in the console. One key covers every entity and the 5,000+ APIs.

.mcp.json

Add the server

Paste the config for Claude Code, Cursor, Codex, ChatGPT or any MCP client.

Ask for an entity

“Get this post”, “publish to three accounts” — the answer comes back in the same shape on every platform.

Connect your agent

Testimonials

You're in good company

Partners and customers across commerce, social and agent tooling.

Customer namePlaceholder

Our agent used to carry one parser per platform. Now it asks AIsa for a post and gets the same fields back wherever it came from.

NameRole, company

Customer namePlaceholder

Every number comes with a source and a date. That is the difference between a metric we can show a client and one we cannot.

NameRole, company

Customer namePlaceholder

We connected over MCP in an afternoon and only pay for the results that come back. No contracts, no vendor research.

NameRole, company

Customer namePlaceholder

Publishing to four platforms is one request now, and the agent never double-posts when a call times out.

NameRole, company

Frequently asked questions

What a resource layer is, what it covers today, and how you pay for it.

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

One schema. Every platform.

Give your agent the resource layer

Connect over MCP in minutes. One schema, every platform, and you only pay for results.

Connect your agent