TokenRoll

1. One-liner

Tracks every tool and stale API token touching your Amazon account, so a suspension appeal has evidence.

2. Trend signal — why now?

On 17 February 2026 Amazon posted a Business Solutions Agreement update to Seller Central. Effective 4 March 2026, a brand-new Section 19 defines “Agents” — automated software or AI systems accessing Amazon Services — and imposes three obligations: an Agent must clearly identify itself as an automated system at all times, must comply with the Agent Policy without exception, and must cease access immediately if Amazon requests. Section 4.2 separately bans using Amazon materials to train or improve AI models, data-mine, or reverse-engineer.

The definition is broad on purpose. Repricers, PPC automation, listing tools, inventory sync, feedback automators, browser extensions and custom scripts all fall inside it. Acceptance is by conduct: continued use of Selling Services after 4 March 2026 constitutes acceptance. There is no formal opt-in.

Three things make this a business rather than a newsletter item.

First, Amazon published no thresholds, no registration, and no penalties. Trade press reporting on the update noted explicitly that Amazon provides no definition of what request volume constitutes an “Agent”, no registration process, no disclosed rate limits and no specified penalties, while granting itself discretionary authority to restrict access without stating criteria. One seller asked in the forum thread whether routine order-pulling software counts as an Agent and got no clarification. Sellers are being asked to comply with a rule whose boundary nobody will draw for them.

Second, liability lands on the seller, not the vendor. Practitioner guidance is blunt that non-compliance is enforceable at the account level, not the tool level — if a repricer violates the Agent Policy, Amazon acts against the Seller Central account, not the vendor’s servers. The seller carries the consequence of a third party’s engineering decision.

Third, the remediation Amazon implicitly demands is a document nobody sells. A law firm advising sellers on this update lays out five steps: inventory every tool that pulls reports, edits listings, changes pricing, runs ads, sends messages or automates operations; document for each whether it uses SP-API credentials, automated login to Seller Central, page scraping that mimics human browsing, or high-frequency bulk requests; obtain written vendor attestation that the system identifies as automated and stops on request; and keep a POA-ready record stating root cause as what tool, what access method, what behavior. That is a product specification written by someone who currently bills hourly to produce it by hand.

Underneath sits an older, unmanaged mess. Practitioner guidance on Seller Central security states plainly that API keys don’t expire when a vendor relationship ends — a former tool provider retains live access until someone manually revokes it, and most brands never audit that list. Amazon does surface an Authorized Partners tab and a User Permissions page, but both are static rosters: they show who may access, never what any of them actually did, when, or by what method. The exact three facts a Plan of Action requires are the three facts Seller Central does not display.

Meanwhile enforcement got faster. 2026 reporting describes Amazon’s systems flagging, suspending and reviewing accounts at high speed using activity-pattern analysis, with bulk requests through third-party tools among the flagged patterns. Suspension appeal services run around $1,495 per case, and one firm sells suspension prevention at $750/month. The money already moves; it just moves to lawyers after the fact.

Market size: roughly 1.65–1.9 million active third-party sellers globally as of early 2026, with over 900,000 using AI tools for listings alone. Fewer than 8,000 sellers generate half of Amazon’s US third-party volume, and the tools those sellers use are almost always automated — so the highest-exposure accounts are also the most tool-saturated.

Provenance:
  - Signal 1 (Demand): Amazon BSA Section 19 effective 4 March 2026 defines "Agents" with no thresholds, no registration, no penalties; sellers publicly confused whether routine tools qualify — https://ppc.land/amazons-new-ai-agent-rules-shake-up-sellers-before-march-4-deadline/ — 2026-02
  - Signal 2 (Feasibility): Amazon SP-API exposes OAuth authorizations, Authorized Partners and revocation endpoints self-serve, so a small team can read a seller's connected-app surface without Amazon partnership approval — https://developer-docs.amazon.com/sp-api/docs/authorizing-selling-partner-api-applications — 2026
  - Signal 3 (Economic): Suspension appeal services priced ~$1,495/case and prevention retainers at $750/mo; law firms publish 5-step tool-inventory + vendor-attestation + POA-documentation checklists they perform manually — https://damlawfirm.com/blog/amazon-bsa-ai-agent-policy-update/ and https://www.amazonsellers.attorney/amazon-suspension-prevention-plan.html — 2026
  Category: Platform shift

3. The opportunity

Amazon created a duty with no instrument. Section 19 makes the seller answerable for the behaviour of every automated system on their account, and Amazon’s own console shows only a permission roster. When the suspension email arrives and asks for a root cause, the seller opens Authorized Partners, sees fourteen app names — four of which they don’t recognise and two of which belong to an agency they fired in 2024 — and has nothing to say.

The incumbents are all on the wrong side of the event. Helium 10, Jungle Scout, Perpetua and the rest are the Agents; they will publish a compliance statement about themselves and stop, because no vendor audits its own installation or grades its competitors’ access methods. Suspension lawyers sell the appeal after the account is down, at $1,495 a go, and their product is a document, not a monitor. Agency platforms like SentryKit watch listings and Buy Box, not the access surface. Nobody occupies the interval between “you connected a tool” and “Amazon asks what it did.”

The wedge is that this is an evidence product, not an optimisation product. Nothing here makes a seller more money on a good day. It makes the bad day survivable, and it does the boring quarterly hygiene — revoking orphaned tokens — that everyone agrees should happen and nobody does. Two forces, one weekly and one catastrophic: stale access accumulating every month, and a suspension that ends the business.

The structural reason it stays defensible for a while: the value is the history. A seller who installs in month one and gets suspended in month nine has nine months of access records a competitor cannot retroactively manufacture. Sign-up date is the moat.

4. Target market

• Primary customer: Amazon third-party sellers doing $500K–$20M annual GMV, and the Amazon agencies managing 5–50 client Seller Centrals. The buyer is the owner-operator or the agency’s ops lead — the person whose name is on the account and who answers the suspension email at 11pm. Concentrated in US, UK, DE and increasingly India-based sellers exporting via Amazon Global Selling.
• Why they buy: Because the account is the business, and they now carry liability for engineering decisions inside software they didn’t write. Their own words, from a seller commenting on the deadline coverage: “another Amazon time sensitive directive. you need a law dept to sell on Amazon, now. none of their hoops and hurdles make the 10% extra in sales worth it.” That seller sold their Amazon business rather than keep up. Others simply don’t know their exposure: the recurring practitioner observation is that a former tool provider retains live access until someone manually revokes it, and most brands never audit that list.
• Rough TAM reasoning: 1.65–1.9M active third-party sellers globally. Filter to those above roughly $500K GMV with a real tool stack and you land in the low hundreds of thousands — call it 150K–250K accounts. Add several thousand agencies each carrying multi-client exposure. Capturing 1,500 of those at $150/mo average is $2.7M ARR, which is the whole target, not a rounding error on it.
• Why now for them: The 4 March 2026 acceptance date has passed and the transition window closed around early June 2026, so enforcement is live rather than theoretical. Every day since then, the seller’s answer to “what accessed your account and how” has been getting less recoverable, because nothing is recording it.

5. Product sketch (MVP)

• Connected-tool inventory. One OAuth connection to Seller Central; TokenRoll enumerates every authorized application and partner on the account, names them, and dates each authorization.
• Orphan-token sweep. Flags authorizations that haven’t been used in 90+ days, belong to a vendor the seller has stopped paying, or were granted by a staff member who no longer has a user account. One-click revoke, with a logged record of the revocation.
• Access-method grading. Each tool in the inventory is classified — sanctioned SP-API, automated Seller Central login, page scraping, or unknown — with a plain-English risk note tied to the Section 19 language. Unknown is treated as a finding, not a blank.
• Vendor attestation tracker. Sends each vendor the written “are you compliant with the Amazon Agent Policy effective 4 March 2026, and does your system identify as automated and cease on request” question, stores the reply, and shows which vendors never answered. Non-response is itself the record.
• Activity ledger. Daily snapshot of what changed on the account — price changes, listing edits, ad-budget moves, messaging bursts — attributed to the tool most likely responsible, timestamped and immutable.
• POA packet export. One button produces the root-cause document in the shape the appeal requires: what tool, what access method, what behaviour, when it started, when it stopped, what was revoked and on what date.
• Kill-switch runbook. A stored, current list of exactly how to sever each connected tool, so “cease access immediately if Amazon requests it” is a two-minute action rather than an afternoon of password resets.
• Agency multi-account view. For agencies: the same ledger across every client Seller Central, with per-client export.

6. AI angle — what’s load-bearing

Two places, both doing real work.

Attribution. The activity ledger sees that at 03:14 UTC 412 prices moved, four listings changed title case, and an ad budget doubled. Amazon does not tell you which connected app did any of it. The model correlates change signatures — timing regularity, field combinations, batch sizes, characteristic formatting — against the known behaviour profiles of the tools on that account to produce an attributed, confidence-scored guess. That is a judgement call across noisy evidence, and it is precisely what a seller cannot do manually across 400,000 events.

Access-method classification. Determining whether a given vendor reaches the account via SP-API, headless login, or scraping requires reading that vendor’s documentation, support pages, changelog and marketing claims and reconciling them against observed request patterns. The model reads the corpus per vendor and produces the classification with citations. This is the part the law firm currently does by hand, per client, per tool.

Remove the AI and you have a static list of app names — which is exactly what Amazon already gives away free. The product only exists because unstructured evidence gets turned into an attributed narrative.

7. Localization angle

N/A — this is a global play. The obligation is Amazon’s contract, not any government’s, so it applies identically to a seller in Ohio, Manchester or Jaipur. The only regional texture worth exploiting is a distribution one: India-based Global Selling exporters are heavily tool-dependent, price-sensitive, and underserved by US-priced suspension lawyers, which makes them an efficient early segment for a $49 tier. Product itself needs no localization beyond English.

8. Business model — path to $1M–$5M ARR

• Pricing: $49/mo Solo (one Seller Central, inventory + orphan sweep + attestation tracker). $149/mo Pro (adds activity ledger with attribution, POA export, kill-switch runbook). $399/mo Agency (up to 15 client accounts, per-client export). Annual billing at 10× monthly.
• ACV: Blended ~$1,800/year, assuming the mix skews to Pro and a meaningful agency tail.
• Rough math to $1M ARR: 560 customers at $149/mo. Or 400 Pro plus 100 Agency. Against a base of 150K+ qualifying sellers, that’s well under half a percent.
• Rough math to $5M ARR: ~2,800 blended customers, which realistically requires two additions: marketplace expansion beyond Amazon (Walmart Marketplace and eBay are running the same automation-governance play), and an incident-response upsell where a live suspension triggers a $500–1,500 assisted POA build — meeting the appeal lawyers at their own price point but with nine months of evidence already in hand.
• Expansion path: Seats → additional marketplaces → client accounts for agencies → incident-response fees. Agencies are the compounding vector: one agency signing brings 5–50 accounts and churns slowly because the ledger becomes the artifact they show clients during onboarding.

9. Go-to-market wedge — first 100 customers

• Free orphan-token audit as the hook. Build a one-click “connect and see who still has access to your account” scan, free forever. It returns a number — “7 tools have live access; 3 haven’t been used in over 90 days; 2 you authorized before 2025” — which is alarming, specific, and true. This is the top of every funnel below. Conversion to paid happens when they want the ledger and the export, not the scan.
• The Seller Central forum thread and its descendants. The February 2026 BSA announcement thread and the trade coverage around it are full of sellers asking whether their tools qualify. Answer those questions publicly and substantively — not with a pitch, with the actual classification for the specific tool they named. Every accurate answer is a demonstration of the classifier. Same play on r/FulfillmentByAmazon and r/AmazonSeller, which run daily suspension threads.
• Agencies first, sellers second. There are a few thousand Amazon agencies; they are enumerable via the Amazon Solution Provider Network directory, agency listicles, and LinkedIn. Each carries multiplied liability across client accounts and has an ops lead who already knows this is a problem. Cold outreach with a free audit run across three of their client accounts, results attached. An agency close is worth 15 seats immediately.
• Partner with the suspension lawyers, don’t fight them. Firms like the ones publishing these 5-step checklists are currently doing steps 1–3 by hand as unbillable prep before the billable appeal. Give them the tool free for their own client intake and take referrals on the way in. Their incentive is aligned: better evidence means higher reinstatement rates, which is what they sell.
• The deadline calendar as content. Amazon ships dated policy changes continuously — handling time June 2026, business-hour delivery rate September 2026, FBA prep changes January 2026. A maintained, accurate “what changes and when” tracker earns the search traffic and the newsletter list that the audit tool converts. This is the slowest channel and the only one that compounds.

10. Build complexity — justification

Low. The SP-API is public, self-serve, well-documented, and OAuth-based — authorization, listing of granted scopes, and revocation are all documented endpoints, and no Amazon partnership approval gates a seller connecting their own account. The activity ledger is polling reports and diffing snapshots. The attribution and classification layers are off-the-shelf model calls over a corpus you assemble by reading vendor docs. There’s no custom infrastructure, no hardware, no regulatory approval. A competent pair ships a credible v1 in 8–10 weeks; the free orphan-token scanner alone is a 2–3 week build and is worth launching by itself.

The genuine work is unglamorous: building and maintaining the vendor behaviour-profile library — a few hundred tools, each needing a documented access method and a change signature. That’s ongoing research effort, not engineering difficulty, and it is also the thing a copycat has to redo from scratch.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Uses sanctioned SP-API with the seller’s own OAuth consent. Reads the seller’s own account data. Explicitly the compliant access method Amazon’s own policy prefers.
Ethical — no harm / dark patterns	✅	Helps sellers understand and reduce their exposure. The free scan tells the truth even when the truth is “you’re fine.”
Market exists (evidence above)	✅	1.65–1.9M active sellers; $1,495/case appeal services and $750/mo prevention retainers already transacting; law firms publishing manual versions of this exact checklist.
1–5 person team can build this	✅	Pair, 8–10 weeks to v1.
Launchable with <$50K / ₹40L	✅	API costs, hosting, model inference. Well under $15K to first revenue.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Account-level liability for third-party behaviour, on the asset that is the business. But it’s felt sharply only at suspension — most days it’s a background dread, not a bleeding wound. The orphan-token angle supplies the weekly hygiene hook that keeps it from being pure insurance.
Demand evidence	15	11/15	Strong indirect evidence: real dated policy, priced appeal market, law firms selling the manual version, documented seller confusion in public forums. Weaker on direct evidence — I found no seller saying “I would pay for an access ledger.” That gap is what the free-scan validation sprint exists to close.
Build feasibility	15	13/15	Public OAuth API, no partnership gate, no custom infra. Points off only for the vendor-profile library being real ongoing work.
Distribution clarity	15	12/15	Free audit hook is concrete and self-demonstrating; agency list is enumerable; lawyer referral loop is aligned. Points off because the forum/subreddit play needs sustained credible presence, not a blast.
Revenue mechanics	15	11/15	Pricing is benchmarked well below the $750/mo prevention retainer and $1,495 appeal, so the value story is easy. But this is a prevention purchase and prevention churns when nothing bad happens — the ledger has to become operationally useful, not just insurance.
Time to first revenue	10	8/10	Free scanner ships in 3 weeks and creates a qualified list immediately; paid conversion realistically 6–8 weeks from launch. Agencies may pre-buy.
Defensibility	10	5/10	Accumulated per-account history and the vendor-profile library are real but modest moats. Any of Helium 10 / Jungle Scout could ship an inventory view — though notably none has, because auditing the tool stack means grading yourself. Execution-and-focus moat with a 9–12 month head start.
Total	100	75/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Technical because the attribution layer over noisy event streams is the whole product and a weak version of it is worthless. Content-heavy because the distribution engine is being visibly, repeatedly right about Amazon policy in the places sellers ask.

Key assumptions to validate (3–5)

1. Assumption: A meaningful share of established sellers have stale or unrecognised authorizations on their account right now. How to test: Run the free scan across 50 volunteer accounts recruited from seller subreddits and agency contacts. Measure the distribution of orphaned authorizations. If the median account has 0–1 stale tokens, the hook is dead and so is most of the urgency.
2. Assumption: Amazon actually asks about tool access during suspension proceedings often enough for the POA export to matter. How to test: Interview 10 suspension consultants and appeal lawyers. Ask directly what fraction of their 2026 cases involved automation or access questions, and whether their clients could answer. If it’s under 15%, reprice around orphan-token hygiene and drop the POA framing.
3. Assumption: Attribution is accurate enough to be trusted. How to test: Instrument 10 accounts with known tool stacks, generate events, and measure attribution precision against ground truth. Below ~80% and the ledger becomes a liability rather than evidence — a wrong root cause in a POA is worse than no POA.
4. Assumption: Sellers will grant OAuth access to a brand-new vendor in order to audit their OAuth access. How to test: Measure connect-rate on the free scanner landing page. This is the sharpest irony in the product and it may bite.

Risk flags

1. Platform dependency (severe): The entire product exists inside Amazon’s contract and API. Amazon could ship a native access log next quarter and vaporise the core view — and unlike third-party vendors, Amazon has both the data and the motive. Mitigation is speed, multi-marketplace expansion, and owning the vendor-profile library Amazon has no reason to build.
2. Enforcement risk: Section 19 has no published penalties. If Amazon never meaningfully enforces it, the urgency evaporates and this becomes a nice-to-have hygiene tool with hygiene-tool pricing. Watch for the first documented Section 19 suspension — that event either makes or breaks the category.
3. Prevention-product churn: Nothing bad happening looks identical to the product not working. Fighting this means making the ledger part of a weekly operating rhythm — the orphan sweep, the vendor attestation chase — not a policy sitting in a drawer.
4. Attribution liability: If the product names the wrong tool as root cause in a submitted POA and the appeal fails, that’s a reputational and possibly legal problem. Confidence scores must be prominent and the export must never overstate certainty.

14. Structured verdict

Score:                  75/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder comfortable with marketplace APIs, paired with
                        someone who will live in seller forums and agency DMs for six months
Time to revenue:        6–8 weeks (free scanner at 3 weeks)
Capital to launch:      $10–15K / ₹9–13L
Top 3 assumptions to validate first:
  1. Median established seller account carries 2+ stale or unrecognised authorizations
     — free scan across 50 volunteer accounts
  2. Automation/access questions appear in 15%+ of 2026 suspension cases
     — 10 interviews with appeal consultants and lawyers
  3. Tool attribution hits 80%+ precision on known stacks
     — instrumented test across 10 accounts with ground truth
Kill criteria:
  - Abandon if the 50-account free scan shows a median of ≤1 stale authorization
    (no hook, no urgency)
  - Abandon if attribution precision stays below 70% after two iterations
    (a wrong root cause is worse than none)
  - Abandon if Amazon ships a native per-app activity log in Seller Central
  - Abandon if fewer than 12 of the first 200 free-scan users convert to paid within
    60 days (prevention framing has failed; the tool is a curiosity)

15. Next step — 1-week validation sprint

• Day 1–2: Build nothing but the OAuth connect flow and the authorization enumerator — the free scan, no UI polish. Simultaneously write the vendor-profile entries for the 25 most common Amazon seller tools by hand, so classification has something real behind it.
• Day 3–4: Recruit 50 sellers from r/FulfillmentByAmazon, r/AmazonSeller and three agency contacts with a single honest offer: “Free, 60 seconds, tells you which tools still have live access to your account. I’m testing whether this is a real problem.” Record for each account: total authorizations, count unused 90+ days, count the seller cannot identify.
• Day 5: Call the 10 sellers with the worst results and ask one question — “would you pay $149/month to keep this current and to have an export ready if Amazon ever asks?” In parallel, email 10 suspension consultants asking what share of their 2026 caseload involved access or automation questions.
• Decide go / no-go on: median stale authorizations ≥2 across the 50 accounts, and ≥3 of 10 interviewed sellers giving an unhedged yes at $149/mo, and ≥2 of 10 consultants confirming access questions appear materially in current cases. Three falsifiable numbers. Miss two of the three and the idea goes in the drawer until the first public Section 19 suspension.