agentcentral
FeaturesPricingDocsSign InStart free trial
Start free trial
DocsUse the feedback tool↓

Start

OverviewClaudeChatGPTOpenClawHermes AgentConfiguration examples

Workflows

Best practicesRun the data tourUse the feedback toolScope your API keysBuild a prompt libraryBusiness playbook

Command line

CLI overviewInstall the CLIAuth and profilesLocal MCP bridgeClient compatibilityAutomationWrite safetyCLI security

REST API

REST API

Platform

How agentcentral worksPricing and billing

Tool Reference

Tool reference overviewAdsInventoryFinanceCatalogRankingFulfillment
Docs

Start

OverviewClaudeChatGPTOpenClawHermes AgentConfiguration examples

Workflows

Best practicesRun the data tourUse the feedback toolScope your API keysBuild a prompt libraryBusiness playbook

Command line

CLI overviewInstall the CLIAuth and profilesLocal MCP bridgeClient compatibilityAutomationWrite safetyCLI security

REST API

REST API

Platform

How agentcentral worksPricing and billing

Tool Reference

Tool reference overviewAdsInventoryFinanceCatalogRankingFulfillment
agentcentral

Product

  • Docs
  • Claude quickstart
  • ChatGPT quickstart
  • Best practices
  • Pricing
  • vs Amazon Ads MCP Server
  • Blog

Tool Reference

  • Ads
  • Inventory
  • Finance
  • Catalog
  • Ranking
  • Fulfillment

Seller Central

  • Amazon Seller Central MCP
  • Amazon Seller Central MCP for Claude
  • ChatGPT with Amazon seller data
  • Connect Seller Central to Claude
  • Connect Seller Central to ChatGPT
  • Amazon Ads MCP server
  • Amazon Ads MCP server for Claude
  • Connect Amazon Ads to Claude

Resources

  • Amazon seller MCP servers compared
  • Amazon MCP server for Claude
  • Amazon MCP server for ChatGPT
  • Amazon seller data layer
  • Amazon Ads agent
  • Start free trial
© 2026 agentcentral. All rights reserved.·Privacy·Terms·DPA·Last updated May 20, 2026

Getting Started

Submit Feedback

Tell agentcentral what worked and what did not, directly from your agent conversation.

The easiest feedback you'll ever send

AI agents are getting better every day, but they still get things wrong. A tool will return stale data, an answer won't match what you see in Seller Central, or your agent will call the wrong tool entirely. When that happens, you don't need to open a support form or write up a bug report yourself (though we do read every email that comes in to support@agentcentral.to).

The quickest way to send us feedback is to ask your agent to do it, right from the conversation where the problem happened.

It will pull together a structured report from the conversation: what you were trying to do, what happened, what should have happened, which tools were involved, and any error messages along the way. Before it sends anything, it shows you a summary and asks you to confirm. Nothing gets submitted without your explicit approval.

Before the report is stored, sensitive information is stripped out automatically. API keys, tokens, connector URLs, buyer names, addresses, phone numbers, emails, order IDs, tracking IDs, and full tool payloads are all redacted. ASINs in free text are aliased. If you left something sensitive in the conversation that you don't want included, you can add a privacy note explaining what was omitted.

The report comes from the conversation itself, which is what makes it different from a typical support form. Your agent has context you'd otherwise have to reconstruct from memory: which tools it called, what date ranges it used, what the responses looked like.

It assembles that into a structured packet with a timeline, evidence, and categorization (tool error, missing data, stale data, confusing tool behavior, permission issue, and a few others).

Every report gets read by a person on our team, and we use what you send to improve the product. If we need more context or want to let you know something was fixed, we'll follow up with you directly.

Try this:

That answer doesn't look right. Submit feedback to agentcentral about what just happened.

Continue Reading

Next: Scope Your API Keys

Give each agent, person, or marketplace the smallest useful tool surface instead of sharing one broad key.

Related Best Practices

Data tour

Run the account data tour to see what data is available, what is syncing, and what needs attention.

Key scoping

Give each agent, person, or marketplace the smallest useful tool surface instead of sharing one broad key.

Prompt library

Turn useful conversations into reusable one-shot prompts with precise dates, metrics, and output formats.

Business playbook

Teach your agent your ACOS targets, lead times, seasonal patterns, and preferred output formats so every conversation starts informed.