Limonene
Investigate Amazon sales, Buy Box, inventory and fees with evidence from your connected store.
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Connect your Limonene store to investigate Amazon sales, dated alerts, Buy Box observations, FBA inventory, and revenue and fees. Ask for a weekly store review, investigate a SKU, or identify stock issues. Results include source context and limitations; missing data is not zero, and revenue after Amazon fees is not net profit. This initial directory connection exposes six read-only investigation tools. It cannot change prices, listings or ads, or export buyer contacts. Sign in with OAuth, authorize one store and marketplace, and revoke access in Limonene. A Limonene account and a connected, synchronized Amazon store are required. Available evidence depends on the store connection. Your AI provider receives requested results under its own data policies. Separately consented management access is an additional rollout and is not part of this six-tool submission.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-20
- Tool count
- 6
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
6 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.