The SP-API gets you halfway. Claude for Chrome gets you the other half. It's really good.
A few of the tools mentioned in this guide are linked with Selling From the Beach affiliate codes. If you sign up through one, we get a small commission at no extra cost to you. We only link tools the SFTB team uses or has tested.
When a tool tells you it is fully connected to Amazon, what they mean is they hit the Selling Partner API. That is the part of Amazon that ships an OpenAPI spec. The rest of Seller Central, the part where you actually run the business, was never on that spec.
Try to file a coupon through the SP-API. There is no endpoint. Try to set up a Brand-Tailored Promotion for your cart abandoners. No endpoint. Try to file a reimbursement claim for a lost shipment, build Premium A+ Content, submit an IP complaint, open a SAFE-T case, change the unit count attribute on a stuck variation, configure a Subscribe and Save discount tier, or appeal an Account Health flag. None of it is on the SP-API. None of it is on the Ads API either.
This is not a list of obscure edge cases. These are the workflows that actually move accounts. Coupons run launches. Brand-Tailored Promotions retain customers. Reimbursements claw back five-figure annual loss. IP complaints protect the brand. They all live in a browser tab.
We audited the SP-API and Ads API in May 2026 against the full Seller Central surface a brand-registered FBA seller actually uses. The APIs cover roughly a third of the day-to-day flows. The other two-thirds, where coupons and brand-tailored and IP and SAFE-T and Premium A+ live, has no spec. It only exists in the browser.
This is the territory Claude Code already owns. Wire up the SP-API and Ads API MCP servers, and these endpoints stop being something you click. They become something the agent does for you on a sentence. The list below is condensed. The actual coverage is bigger, but these are the surfaces real sellers spend time on.
| What the agent can do | Endpoint or report type |
|---|---|
| Patch listings (title, bullets, images, attributes) | Listings Items v2021-08-01 |
| Pull live FBA inventory by SKU and FC | FBA Inventory v1 |
| Create FBA inbound shipments end-to-end | Fulfillment Inbound v2024-03-20 |
| Create AWD inbound, confirm, get labels | AWD v2024-05-09 |
| Submit MCF orders with BLOCK_AMZL feature | Fulfillment Outbound v2020-07-01 |
| Read sales and orders, hourly to monthly | Sales / Orders / Reports APIs |
| Pull Brand Analytics search terms, repeat purchase, market basket, search query, search catalog | GET_BRAND_ANALYTICS_* |
| Pull coupon and promotion performance reports (read) | GET_COUPON_PERFORMANCE_REPORT |
| Create Sponsored Products campaigns, ad groups, keywords, negatives | Amazon Ads v3 SP |
| Create Sponsored Brands v4 ads (image, headline, three products) | Amazon Ads v4 SB |
| Create Sponsored Display multi-asset creative | Amazon Ads SD |
| Pull pricing, BSR, catalog metadata, fee preview | Catalog / Pricing / Product Fees |
| Subscribe to event webhooks (inventory, offers, account) | Notifications v1 |
| Run AMC queries for advertiser cohorts | Amazon Marketing Cloud |
| Send buyer-seller messages within allowed templates | Messaging v1 |
That covers the ad spend, the inventory, the catalog, the orders, and the analytics. For a lot of operators, this is already most of what "running the account" looks like, plus the P and L overlay from something like Sellerboard sitting on top.
But it is not all of it. Not even close.
Here is the rest of the seller surface, grouped by what kind of work it represents. Every item on this list lives in a Seller Central tab, an Ads console screen, or a Brand Registry portal. None of it ships an OpenAPI spec. None of it answers to an API key.
Some of the tools in this category already have niche SaaS layers built on top of the gap. Reimbursements have Seller Investigators. Review removal has TraceFuse. These are evidence the gap is real and the workflow is valuable. They are not on the SP-API because the SP-API does not file claims.
Claude for Chrome is the browser extension version of the agent. It sees the page you see. It clicks the buttons you click. It fills the forms you fill. It is the missing layer over the UI-only third of Seller Central.
It reads the rendered HTML of whatever tab you have open, locates elements by text or role, and acts. Click "Create coupon." Pick a budget. Pick a discount type. Select ASINs. Submit. On the way through, it can pull data from your other tools to make the decision: launch ASIN list from a spreadsheet, FBA on-hand from sp-api, budget from a number you told it to follow.
What it does not do is replace your judgment. It does not bypass two-factor auth. It does not solve CAPTCHA. It runs at human pace, in your logged-in session, while you watch.
The SP-API turned data into endpoints. Claude for Chrome turns everything else into endpoints too.
Two APIs are the back-office stack: data, ads, listings, inventory. Claude for Chrome is the front-office stack: every human-touch workflow Amazon never opened up. Both, side-by-side, talking to the same agent, is the first time a single chat session can run the account.
Concrete examples of jobs the composite stack now handles end-to-end. Each one used to be a person on a browser tab, working a checklist. Now it is one prompt.
The most-clicked-on workflow in any Amazon launch. Twelve clicks per ASIN times every ASIN in the launch. No API. Now it is one sentence.
Log in. Coupons. New. Pick ASIN. Pick percentage. Pick budget. Pick start date. Pick targeting. Review. Submit. Repeat per ASIN.
"File a 20 percent coupon on these 6 launch ASINs, 500 dollar budget each, start Monday." The agent opens the tab, walks the form for each, reports back the live coupon IDs.
The SP-API can read the reimbursement events. It cannot create a claim. Every lost-shipment or damaged-return discrepancy is a separate case form.
Pull the discrepancy report. Open each row. Open a case. Paste the FNSKU, the shipment ID, the quantity, the dollar amount. Submit. Wait.
Agent reads the discrepancy report via sp-api, opens the case form via Chrome, files each one, logs the case ID per row. Or skip the build and use Seller Investigators.
Cart Abandoners. Recent Viewers. Repeat Customers. Nine audience types. Zero API. Maximum retention leverage, maximum manual cost.
Brand portal. Customer Engagement. Brand-Tailored Promotions. Pick audience. Pick ASINs. Pick percentage. Pick term. Submit. Wait for the next one to be eligible.
"Run a 15 percent Cart Abandoners promo on these ASINs for the next 30 days." Agent walks the multi-step form, picks the audience, applies the ASIN set, submits.
The brand-protection workflow the SP-API does not touch. Every counterfeit listing is a separate report-a-violation form.
Find counterfeit ASIN. Open Brand Registry. Report a Violation. Pick infringement type. Paste evidence. Paste trademark reg number. Paste ASIN. Submit. Repeat per offender.
"For each ASIN in this list, file an IP complaint citing our USPTO 12345678 trademark." Agent walks the form per offender with the same evidence block, logs the violation IDs.
The SP-API can only create Standard A+ modules. Premium A+ tiers, including Brand Story, are not in the contentModuleType enum at all. UI only, no exceptions.
Open A+ Manager. New module. Pick Premium template. Upload assets. Position. Save draft. Submit. Wait for moderation per ASIN family.
"Build a Premium A+ doc for the Hammam line using the assets in this folder, link to these 4 ASINs." Agent assembles in the UI, links via SP-API once moderated.
Five steps from a blank machine to running the account from chat. Each one is a thing you do once and forget. If you already use Claude Code with an MCP server, you can skip the first two.
Ask the agent three things in a row: show FBA inventory for an ASIN (sp-api), show 30-day Sponsored Products spend by campaign (ads-api), open Seller Central and screenshot the Coupons page (Chrome). If all three return real data, the stack is live.
The composite stack is not magic. There are still surfaces where the agent has to wait for you, defer to a person, or stop entirely. Knowing where the line is keeps the rest of the stack trustworthy.
If the workflow is filling out a form Amazon already designed, the agent owns it. If the workflow is deciding what to put in the form, you still own it. The composite stack moves the line between thought and execution, not between judgment and ignorance.
The full reference, by category. Pin this. When someone tells you their automation tool is "fully connected to Amazon," check what side of this list they actually cover.
| Domain | Surface (UI-only, Claude for Chrome closes it) |
|---|---|
| Promotions | Coupons. Brand-Tailored Promotions (9 audience types). Lightning, 7-Day, Best, Outlet Deals creation. Prime Exclusive Discounts. Subscribe and Save tier setup. Legacy Manage Promotions. Social Media Promo Codes. Manage Your Experiments. Vine enrollment. |
| A+ and Stores | Premium A+ creation. Brand Story module creation. Store Builder layout, tiles, drafts, scheduled publish. Product video uploads to detail pages. |
| Brand Registry | Brand Registry enrollment. GTIN Exemption. Brand Gating / Apply to Sell. IP complaints / Report a Violation. Project Zero. Transparency. |
| FBA | Reimbursement claim creation. IPI appeals. Storage limit appeals. Aged Inventory Surcharge disputes. IPS waivers. Sourcing Cost uploads. Stranded inventory cause-fix. New Selection enrollment. |
| AWD | Manufacturer Central Direct inbound. Bin-level visibility. Per-replenishment tracking. Storage rate negotiations. |
| Catalog | Variation family restructuring (restricted categories). Browse node corrections. ASIN merges and splits. Featured Offer loss diagnostics. Pricing eligibility appeals. High-price error appeals. Pan-EU parity gating. |
| Customer Service | Per-SKU return policies. SAFE-T claim filing. A-to-z representments. Chargeback representments. Refund-at-first-scan policy. Brand review replies. Vine review removal. |
| Account Health | Account Health Rating appeals. Section 3 violation appeals. Suspension Plans of Action. Restricted Products approvals. Performance notification responses. |
| Tax & Banking | Bank / deposit / charge method changes. W-9, W-8BEN-E updates. VAT, GST, MTC uploads. Disbursement schedule and reserve appeals. |
| International | Build International Listings config. Pan-EU enrollment, country activation. NARF enrollment, exclusions. |
| Settings | Notification preferences (human-facing). User permissions, sub-accounts. Two-factor, recovery, login devices. |
One spec for the data plane, one extension for the human plane, one chat in the middle. That is what total control looks like in 2026.
The field map will rot. Amazon will ship a new surface, deprecate an old one, open up an API we said was UI-only. This deep dive is a living document.
If you build the composite stack and find a workflow we missed, or a UI surface that quietly got its own SP-API endpoint, write back. We update the map and the next version cites you.