Atualizações Brief Policy
Amazon Ads AI-agent language in the BSA (4 March 2026)
A Amazon publica avisos da Seller Central e Ads em inglês. O brief abaixo permanece em inglês para não perder o texto-fonte. Revisão, formulários e políticas estão no seu idioma. Confirme números na Seller Central.
Who it hits
Anyone running Xnurta, Flywheel, Cobalt, or scripts against the Ads API.
What to do this week
Keep a human on kill rules. Log automation moves. Do not let an agent hold production Ads credentials in a chat window.
What we will not do
- Paste Seller Central passwords into a model.
- Turn on catalog-wide target ACOS in an agent and walk away.
- Call a dashboard login “management.”
Stack pages: Xnurta, Claude, Cursor.
What the March 2026 BSA language is for
Amazon’s Business Solutions Agreement grew explicit expectations around AI agents and automated software acting in the account. Read the live agreement — this page is the operator translation, not a legal memo. Automation is allowed. Abdication is not. Bid robots (Xnurta, Flywheel, Cobalt, scripts on the Ads API) are still your problem. Unsupervised “max ROAS” on a blended auto campaign is still a leak. unBoxed 2025’s Ads Agent that drafts AMC SQL does not change the rule: a human reviews, a human runs, production credentials do not live in a chat log.
How this desk uses models
Claude, Codex, Kimi, and Cursor draft from exports. They do not log into Seller Central or Ads Console. They do not hold 2FA. They do not get a catalog-wide target ACOS. Xnurta / Flywheel / Cobalt execute inside contribution rails you set after Fee Preview. Kill rules stay human. The founder log names who changed a ceiling. That is enough to stay on the right side of “automated systems acting in the account” without pretending a chatbot is the account manager.
What we will not do
- Paste Seller Central or Ads passwords into a model.
- Turn on catalog-wide target ACOS in an agent and walk away.
- Call a dashboard login “management.”
- Let an Ads Agent ship SQL to production without a read of the join.
Stack: Xnurta, Claude, Codex, Kimi, Cursor. Confirm the live BSA; Amazon will edit it again.
A weekly check that keeps automation honest
List every tool that can change a bid: Xnurta, Flywheel, Cobalt, scripts, an Ads Agent. Next to each, write the contribution ceiling and who last changed it. If a model drafted SQL or a harvest file, the founder log names the human who ran it. That is the operating translation of “automated systems acting in the account.” A dashboard login is not management. Turning automation off is not required. Owning the rails is. Confirm the live BSA; this page will lag the next edit.
Operator translation, not a legal memo
Amazon’s Business Solutions Agreement grew explicit expectations around AI agents and automated software acting in the account. Read the live agreement. Automation is allowed. Abdication is not. Bid robots (Xnurta, Flywheel, Cobalt, Ads API scripts) are still your problem. Unsupervised catalog-wide target ACOS on blended auto is still a leak. unBoxed 2025’s Ads Agent that drafts AMC SQL does not change the rule: a human reviews, a human runs, production credentials do not live in a chat log. A CSV export with no passwords is how this desk drafts. Logging a model into Seller Central or Ads Console is the line. Confirm the live BSA; this page will lag the next edit.
FAQ
Is using ChatGPT on a search-term CSV a BSA violation?
A CSV export with no passwords is how this desk drafts. Logging the model into the account is the line. Read the live agreement for the formal wording.
Do I have to turn automation off?
No. You have to own the rails. Automation without a contribution ceiling is the problem, not the existence of an API token.
Source: Amazon BSA / Ads policy updates, Mar 2026 (confirm live agreement) · Confirm live numbers in Seller Central. This desk is the method, not a rate card.
Stuck on this change?
I will walk the public listing, say whether this change is leaking spend, and what week one would be.