Amazon seller data API for AI agents

Your AI is smart. It just can't see your Amazon data.

A managed Amazon data warehouse and read-only API for the AI you already run. Your agent reads ads, sales and search data in one place, then builds on it: dashboards, Slack alerts, weekly profit reports. No credits, and your data never routes through a model you did not pick.

The same data layer SellerPlex runs its own PPC, supply chain and account health teams on.

Amazon Ads Verified Partner Amazon SPN Certified
+ anything that can call an API
Claude
Build me a board of search terms that spend money without orders
commerce-spine · search terms + productPerformance · 1,284 terms ✓
Built it as an artifact. 37 search terms spent money this month without a single order. wasted-spend · artifactOpen ↗ $412large hiking backpack0 ORDERS $288chef knife gift set0 ORDERS $96dog harness no pull2 ORDERS
Have it email me every Monday
scheduled · weekly digest ✓
Scheduled. It re-queries your live warehouse each Monday, so the numbers are never stale. Wasted Spend WatchWEEKLY 37search terms with spend and no orders runs Mondays 07:00read-only
Reply to Claude…Fable 5

Conversations shown are synthetic.

Live on the data layer

The brands already running on Commerce Spine

all about juicingcooking gift set coelephantstocketta vitaidetectmenfirstminisplits4lessnutravilleoptimal carnivorepurify lifesinless snacksswitch supplementsvidal craftswashi tape shopyellow mountain imports
casablanca marketcross and gloryessential stacksheadlight glasseskerala botanicsmilk snobnew healthnutravospurely northwestsheer strength labssitka farmsthird eye cacaowall charmerswavesrxzentoes

Right now you have two bad options.

Option A

Export and paste

Download the Seller Central report. Download the Ads report. Paste both into your agent and hope the context window holds. The data is stale before you finish, nothing joins to anything, and next week you do it all again.

Option B

Rent a bundled AI

Sign up for an all-in-one tool and you get someone else's chat window, someone else's model routing, and a credit meter that decides how many questions you are allowed to ask about your own business. Run out mid-analysis and the answer is: upgrade.

The agent you already run can reason about your business just fine. It simply has nothing to read.

Connect Amazon seller data to your AI.

Amazon does not give you one API. It gives you Ads, Seller Central, Vendor Central, Brand Analytics, DSP and Marketing Stream, each with its own auth, shapes, quirks and rate limits. We absorb all of that and hand your agent a single interface. And we are not a connector. A connector proxies live endpoints and forgets everything the moment the call ends. This is a warehouse: your history is stored, joined across sources and query-ready, so your agent can compare this week to last quarter without re-pulling anything.

1

Connect your Amazon accounts

Authorize Ads, Seller Central and Vendor Central through Amazon. We never see your login.

2

We build your warehouse

We backfill 30 days, then keep syncing. Everything is cleaned and joined across sources.

3

Query from your own AI

Install the plugin, add your token. Your agent gets the full data dictionary: 316 documented columns.

Amazon Ads + DSP Marketing Stream Seller Central Vendor Central Brand Analytics COMMERCE SPINE WAREHOUSE cleaned + normalized joined across sources full history, kept refreshed daily AI-first API read-only · scoped tokens your agent Claude Code Codex · Cursor YOUR AMAZON DATA WE MAINTAIN THIS YOU KEEP THIS

Querying is step one. Building is the point.

Any data tool can answer "what is my ACOS". The reason to put this data inside a coding agent is that the agent does not stop at the answer. It writes the thing that watches the number for you, and it keeps running after you close the laptop.

Dashboard

A wasted-spend board that updates itself

Your agent reads search terms and spend, writes the dashboard and points it at your live warehouse. You open a URL, not a spreadsheet.

Alert

Account health warnings in Slack

A scheduled check that posts when a listing goes inactive or a buy box drops. Written once, running from then on.

Report

Monday profit summary, per marketplace

A cron your agent wrote against a versioned API, so the same query returns the same shape every week and the report does not quietly break.

Tool

Whatever your operation actually needs

Negative keyword sweeps, margin rollups across brands, an internal tool for your VA. If your agent can write it, it can run it on this data.

You also get the skills our own agency runs on.

This is the part competitors cannot copy quickly. SellerPlex runs a full Amazon agency, and our PPC, supply chain and account health teams have spent years building the analysis methods they use daily. Those same skills and agents ship inside your subscription, so your agent starts out sounding like someone who runs accounts for a living instead of a blank model with database access.

PPC Semantic Analyst

Root-caused, prioritized insights instead of a metrics dump. Tells you what moved, why, and what to look at first.

Ads Query Orchestrator

Plans multi-step pulls across tables so your agent does not reinvent the joins every session.

Profit-First PPC Analyst

Recommendations ranked by profit impact, using real fee and cost data from the warehouse.

Amazon Ads Entities

A conceptual map of the Ads hierarchy, portfolio to target, linked to the selling entities it spends against.

Amazon seller data coverage and refresh rates.

Stop stitching exports. Ads, retail and search data arrive joined and query-ready, with your history intact.

10
query-ready entities today
316
documented columns your agent understands
30 days
backfilled at first sync
6
Amazon sources joined for you
Amazon Ads APISponsored Products, Sponsored Brands and Sponsored Display, campaign through search-term grain.
Marketing StreamTraffic and conversion signal from Amazon Ads.
Seller CentralSales and traffic, listings and account data.
Vendor Central + CatalogRetail analytics, shipments and the catalog metadata everything joins back to.
Brand AnalyticsSearch query performance, catalog share and shopper behavior.
Amazon DSPProgrammatic campaign, audience, inventory and creative reports.

One catalog, one contract

EntitiesTyped, deduplicated and joined across sources, with derived metrics computed for you.
History30 days backfilled at first sync, then kept from that day forward, so it compounds.

Freshness, published

Performance rollupsdaily
Brand Analyticsweekly

Questions your agent can finally answer.

Just ask, or tell it what to build. Everything stays read-only: your agent drafts and reports, you decide what happens in your account.

ppc> Root-cause the ACOS jump on our top 10 parents last week. Campaign by campaign, with the numbers.
search terms> Which search terms burned spend with zero orders this month? Rank by wasted dollars.
brand analytics> Compare our branded search query share against the category for the last 8 weeks.
ppc> Which campaigns spent more than last month with fewer orders?
portfolio> Rank every client account by margin change this month. Flag the two that need a call today.
reporting> Write a cron that posts a Monday profit summary per client to our Slack.
ppc digest> Every Friday, email each account manager their ACOS by campaign type, week over week. Flag anything that moved more than 10%.
onboarding> New client connected yesterday. Summarize the account: top ASINs, spend structure, obvious leaks.
retail analytics> Show sell-in versus sell-through by ASIN for the last 13 weeks. Where is inventory piling up?
catalog> Which of our listings lost the buy box or changed availability this week?
brand analytics> Where do shoppers go when they search our brand and don't buy us?
retail analytics> Which ASINs lost sell-through share in the last four weeks?
rank watch> Check our branded search share weekly and alert me the moment a competitor takes the top spot.
bid proposals> Draft bid-change proposals for every keyword above target ACOS, as a CSV I can review.
integrations> Pull yesterday's ad spend and orders per marketplace into our BI tool every morning.
Chat is where you explore. Code is where it compounds. Because the API has a versioned contract, the same query returns the same shape every time. Your agent can write scripts and scheduled jobs that keep working, instead of chat sessions that evaporate.

Amazon data API pricing. No credits.

Price is not the reason to pick this, and we would rather you chose us for the data quality. But the pricing model matters, because credit systems meter your curiosity. Nobody can tell you what a credit buys before you spend it, and the meter always runs out in the middle of the analysis that mattered. We think that is a bad way to treat an operator.

Commerce Spine is a flat monthly subscription. Price scales with data volume: how many brand accounts and marketplaces you connect. It never scales with how many questions you ask.

There is a free tier, and it is a real product. One connected Amazon account, 30 days of history, the full catalog and the full API. Not a trial that expires, not a sandbox with fake data. The caps are printed below, the same way the paid caps are.

Your AI costs stay yours. You already pay Anthropic or OpenAI for a model you trust. Keep doing that, at their prices, on the plan you have. We will never mark up tokens or route your data through a model you did not pick.

Your bill should be the most boring thing about your data stack.

What flat actually means
FreePaid
Connected accounts13 to 12
History backfilled30 days30 days
Requests per hour203,600
Requests per day401,000
Date window per query30 days90 days
Data scanned per month1.5 GB150 GB
Rows per page500500
Query timeout60 s60 s
Applied per organization, not per token, so minting more keys does not buy more quota. Printed here, enforced in the API, no overage billing. Amazon caps historical data at 90 days; we backfill 30 at first sync for every account and keep everything from that day forward, so your history compounds.

Launch pricing

Start free on one account, upgrade when you connect the second. Both paid plans include 5 hours with one of our senior AI developers, for onboarding, for porting what you already built, and for standing up your first dashboard or alert with you.

Brand
$49/mo

Up to 3 connected accounts (brand and marketplace pairs). 1,000 queries a day instead of 40, a 90-day query window, 150 GB scanned instead of 1.5, all included skills, and 5 hours of senior AI developer time.

Start on Brand
Portfolio
$149/mo

Up to 12 connected accounts across brands and marketplaces, priority support, 5 hours of senior AI developer time, everything in Brand.

Start on Portfolio

Free accounts let us read the connected account to build you a tailored growth proposal. That is the trade, and it is the only thing free costs you. Running more than 12 accounts, or an agency? Talk to us, portfolio pricing scales with connections, not questions.

Read-only by design. Your model by choice.

The API cannot write

Tokens are read-only. Commerce Spine cannot touch your bids, listings, prices or inventory. Nothing we ship can take an action on your account.

Scoped access

Tokens are scoped per account and marketplace. Team management in the console controls who holds which token. Revoke instantly.

Your model, your terms

Your prompts and query results go to the model you chose, under your agreement with that provider. We never see your conversations and never proxy your AI traffic.

Standard Amazon consent

Access is granted through Amazon's own authorization flow and revocable there at any time. Your data lives in a managed, isolated data warehouse on Google Cloud.

Agency and software, kept apart

SellerPlex runs an agency too, so we built for that objection: your warehouse is segregated per organization and the agency side has no path into it. Maintenance access sits with the engineers who run the infrastructure, nobody else.

Tools that promise an AI will "run your business" need write access to everything and your trust in an autonomous model. We deliberately built the opposite: a data layer rich enough that you decide what actions to take, in code you wrote, that you can read.

The data layer our own agency runs on.

SellerPlex is a full-service Amazon agency. Our PPC, supply chain and account health departments run their daily work on this exact warehouse and API, using these same skills, against client accounts with real money on the line, every day.

The schema is shaped by people who actually operate accounts, so the joins you need exist and the rollups answer real questions. And when Amazon changes an API or a report format, we feel it the same morning you would, and we fix it because our own teams are blocked too.

We productized our own infrastructure. The alternative was watching everyone duct-tape their own version of it. And it keeps compounding: what we build for our own teams this quarter shows up as a Commerce Spine feature next.

PPC

Bid and budget decisions grounded in the profit-first skill set, across every client account.

Supply chain

Shipment and margin planning on the same warehouse.

Account health

Monitoring built on the same event pipeline.

Thin on purpose.

Other tools make the web app the product and lock your workflow inside it. Ours does five jobs and then gets out of the way. The real interface is the one you already live in. We are not going to build a worse chat window than the one on your machine.

Commerce Spine console: data catalog with per-table freshness, connected accounts, API tokens, team and skills
Data catalog + freshness Connect Amazon accounts API tokens Team management Skills library

"Couldn't I just build this myself?"

It is the first question every technical buyer asks, and it deserves a straight answer rather than a sales one. Yes, you could. Here is what building on the Amazon SP-API actually costs.

01

Amazon has to approve you first

Most of the useful data sits behind an application you must build, submit and get approved on Amazon's marketplace. That is paperwork you cannot code around. We already carry that approval, so you skip it entirely.

02

The hard part is the architecture, not the code

Pulling a report is a weekend. Making millions of rows across Ads, Seller Central and Brand Analytics land clean, joined and consistent enough that an agent can reason over them without burning tokens or contradicting itself is a different problem. Ours took months of full-time work by people who do this for a living.

03

It never stops needing maintenance

Amazon changes report formats, deprecates endpoints and shifts fields. Every one of those is an evening you spend repairing a pipeline instead of running your business. When it breaks for us, our own agency is blocked too, so it gets fixed that morning.

04

You are buying back the boring part

You keep the interesting work: the analysis, the automations, the tools your agent writes on top. You hand off the ingestion, the schema drift, the retries and the access management. That is the whole trade.

05

Already built something? That is the normal case

Most people we talk to have already wired up some version of this, and the real question is not whether ours is better in theory but what switching costs them. That is exactly what the included developer hours are for: one of our senior AI developers sits with you and ports what you already have onto the warehouse, so you are not rebuilding your own tooling on your own time.

Pick your data layer deliberately.

Bundled AI toolsDIY SP-API pipelineCommerce Spine
AI modelTheirs, routed for youYoursYours
Pricing meterCredits, undefined per taskEngineering time, infrastructure and maintenanceFlat: $0 for 1 account, $49/mo for up to 3, $149/mo for up to 12, limits published
InterfaceTheir chat windowWhatever you buildYour agent, plugin plus skills
Data depthWhat their UI surfacesWhat you have time to pipelineA full warehouse joined across Ads, retail and Brand Analytics; 10 curated entities
Scripts and cronsLocked to their workflow builderYes, you maintain itYes, a stable versioned API, we maintain it
Works with your other toolsLimited to the integrations they chose to buildYou build every connector yourselfNaturally: your agent joins Commerce Spine data with any API it can reach, from Data Dive to your ERP, CRM or own databases
Write access to your accountUsually requiredYour callNone, read-only by design
When Amazon changes an APIThey fix it, eventuallyYou fix it, at 2amWe feel it the same morning you do, our own agency is blocked until it's fixed

If you want an AI that clicks buttons for you, we are not it. If you want your AI to finally know what is happening in your account, keep reading.

Commerce Spine questions and answers.

What is Commerce Spine?
Commerce Spine is SellerPlex's managed Amazon data warehouse and read-only API for sellers, agencies, vendors and AI builders. It stores and joins Amazon account data so your own AI agent can query it and build reports, dashboards and alerts. Start with how it works, check data coverage, or compare plans and limits.
Why is there no chat UI or bundled AI?
Because you already have one you like. Bundled AI means someone else picks the model, routes your data through it, and meters your usage in credits. Commerce Spine ships as a plugin, skills, and an API token for the harness you already run: Claude Code, Codex, Cursor, or anything that can call an API. We would rather be the best data layer than the fourth-best chat window.
Which AI tools does it work with?
Anything that can hold an API token and make an API call. The official plugin gives Claude Desktop and Claude Code first-class access: install it, sign in once, and your agent knows the full data dictionary. From Codex, Cursor, custom agents or plain scripts you use the same read-only API directly with a scoped token, and the documented schema makes that straightforward. If your setup can make an HTTPS request, it can query your warehouse.
Why can't I just vibe-code this myself?
You can absolutely stack Amazon exports into your own database, and for a weekend project that works. The problem is not the first build, it is the second year of owning it. The Amazon API surface is genuinely complex, and the data volume needs real infrastructure: constant updates, curation and organization before an agent can use it reliably. Vibe-coded pipelines tend to end up expensive, token-heavy and inconsistent, because the hard part is not the code, it is the underlying architecture. Ours took months to tune, full time, by people who do this for a living. There is also paperwork you cannot code around: most of the deeper Amazon data requires an approved application in Amazon's marketplace. Commerce Spine already carries that approval. Then there is the part nobody budgets for: Amazon changes report formats, deprecates endpoints and shifts fields, and every one of those is an evening you spend repairing a pipeline instead of running your business. That maintenance never ends, and it is the actual cost of the DIY route. You plug in and start building; the operational headache stays ours.
How is pricing metered?
Flat monthly subscription, priced by connected accounts. Free is one connected account, 30 days of backfilled history, 20 requests per hour, 40 per day, a 30-day window per query and 1.5 GB scanned per month. Paid is $49/mo for up to 3 connected accounts (brand and marketplace pairs) and $149/mo for up to 12, with custom pricing above that: 60 requests per minute, 1,000 per day, a 90-day window per query, and 150 GB scanned per month. First sync backfills 30 days on every plan, which is what Amazon releases in practice against a 90-day ceiling, and everything from that day forward is kept. Both paid plans include 5 hours with one of our senior AI developers, usable for onboarding, for migrating tooling you already built, or for standing up your first dashboards and alerts. Limits are applied per organization rather than per token, so extra keys do not buy extra quota. No credits, no overages, no per-seat fees. Your AI token costs are paid by you, directly to your model provider, exactly as they are today.
Can Commerce Spine change anything in my Amazon account?
No. The API is read-only by design and tokens cannot write. Bids, listings, prices and inventory are untouchable through Commerce Spine. If you want to act on an insight, you do it through your own tools and your own code, where you can read every line before it runs.
How fresh is the data?
As fresh as Amazon allows: performance rollups daily, Brand Analytics weekly. Every live entity in the console shows its last successful sync, so you never have to guess whether a number is current.
How is this different from bundled AI seller tools?
Tools in that category bundle a chat AI, workflows and data behind one login and meter everything in credits, with model routing they control. Commerce Spine is the opposite architecture: we do the data layer only, expose it through a read-only AI-first API, and you bring your own AI on your own subscription. No captive UI, no credit meter, and your data only ever goes to the model you chose. If you are comparing us against a specific tool you already pay for, ask us on a call and we will walk through it honestly. Our DataHawk alternative page does that for one of them.
Are you a connector, or a warehouse?
A warehouse, and the difference decides what your agent can actually do. A connector proxies Amazon's live endpoints: it asks the question, hands back the answer and keeps nothing, so there is no history, no joins across sources, and every comparison means re-pulling data you already fetched. We ingest from all six Amazon sources into storage you own a slice of, clean and normalize it, join it so a campaign row can meet an inventory row, and keep it. That is why your agent can answer "compare this week against the same week last quarter, by brand" in one query instead of orchestrating a dozen calls and hoping the rate limits hold.
Why use a managed Amazon data API instead of building on SP-API?
Amazon's Selling Partner API provides programmatic access to seller and vendor data. Building on the Amazon SP-API yourself means maintaining authorization, ingestion, retries, storage and joins across the sources you use. Commerce Spine maintains that warehouse and exposes a read-only API. Its GraphQL interface lets your agent request named fields and entities. Every plan backfills 30 days at first sync, then retains data from that point forward. An MCP server is an interface to tools and data; it does not, by itself, provide this storage or maintenance. See the official Amazon SP-API overview and Commerce Spine API documentation.
Does Commerce Spine require an MCP server?
No. Claude Desktop and Claude Code use the official Commerce Spine plugin. Codex, Cursor, custom agents and scripts can call the same read-only API directly with a scoped token. MCP is a protocol for connecting AI applications to tools and data; it does not inherently require another AI model or an extra model fee. Commerce Spine's distinction is the managed warehouse and documented API underneath your agent. Read the MCP architecture overview for how the protocol works.
SellerPlex is also an agency. Can its people see my data?
No, and we understand why you are asking: an agency that also sells you software is exactly where you should push. Two things keep it clean. First, isolation by architecture: every organization gets its own segregated warehouse, so there is no shared pool where your numbers could sit next to a SellerPlex client's. Second, separation by department: the agency side of SellerPlex has no path to customer warehouses. The people who can touch the infrastructure are the engineers who maintain it, for maintenance only, the same arrangement you already accept from every database vendor you use. On your side, access is limited to the people you invite through Team roles and the scoped API tokens you issue, every request is logged with the token that made it, and you can revoke any token instantly.
Where does my data live and who can see it?
Your data lives in a managed data warehouse on Google Cloud, connected through Amazon's own consent flow, which you can revoke at any time. Access on your side is controlled by scoped, revocable API tokens and console team management. Your prompts and query results flow between your machine and your chosen model provider under your agreement with them. We never proxy or read your AI conversations.

Get started for free. One account, no card, no expiry.

We onboard in small cohorts so every backfill, every schema question and every skill gets attention from the team that built it. Bring the AI you already run. We will bring the data.

  • Free forever on one connected account
  • Read-only API, your model, your harness
  • 5 hours with a senior AI developer on every paid plan
  • Cancel anytime

Prefer to talk first? Book a demo.

Step 1 of 4

How many ASINs are you running?

Sizes your warehouse and backfill

Required
Required
Enter a valid email
Required
Marketplaces
Pick at least one
Pick one
✓

You're in

Onboarding call booked. Watch your inbox for the confirmation and your warehouse setup details.