Platform
How agentcentral works
agentcentral syncs your Amazon seller data ahead of time and serves it to your agent through MCP tools. Most reads return in under 300ms. Writes go through Amazon's API with guardrails, preview, and an audit trail.
How data flows
Data freshness
Your Amazon data syncs on a schedule that varies by type. These timelines matter because querying data before it has fully settled can produce misleading numbers.
| Data | Lag | Refresh |
|---|---|---|
| Ads (SP, SB, SD) | 14-day attribution window | Daily |
| Business Reports | ~72 hours | Varies |
| Sales summary | Hours | Varies |
| Orders | None at the source | Varies |
| Inventory | Snapshot, not a stream | Varies |
| Search Query Performance | Weekly granularity | Varies by plan |
| Keyword ranks | As of last snapshot | Varies by plan |
| Settlements | Settlement period | Varies by plan |
Refresh frequency can vary with marketplace activity. For what is loaded right now rather than what is typical, each connected marketplace shows its own last-refresh state in the dashboard, and the /v1/freshness endpoint reports the most recent date available per data source.
Live API tools
Most tools read from synced data and return results in 100-300ms. A subset call the Amazon API directly for live data. These are slower (200-800ms) and subject to Amazon's rate limits.
Three tools — get_buybox_status, get_competitive_pricing, and get_subscribe_and_save — default to live mode but switch to stored history when you pass start_date or end_date.
Live API tools are tagged as live api or hybrid in the tool reference.
Search Query Performance
Search Query Performance (SQP) data from Brand Analytics uses weekly granularity. Each row covers a full Amazon week, not arbitrary date ranges. Querying a single day returns the entire week that contains it.
This also affects keyword rank queries with the with_volume view, which joins rank snapshots with the SQP week containing each snapshot date. The volume numbers represent the full week, not the individual day.
Write operations
Guardrails
Every write tool enforces safety limits, requires a preview step before submission, and logs the action with old and new values.
| Limit | Value |
|---|---|
| Bid range | $0.02 to $100 |
| Budget range | $1 to $10,000 |
| Placement bid range | 0% to 900% |
| Change warning | Flags changes over 500% from current value |
| Batch size | 100 ads items, 25 price/quantity updates, 20 listing patches |
| Confirmation | Preview, confirm, and idempotency key required before submission |
Querying
Marketplace and profile selection
Your account is connected to one or more Amazon marketplaces. For advertising tools, each marketplace maps to an Amazon Ads profile. The profile_id parameter controls which profile's data you query.
- Omit profile_id: queries across all profiles for your connected marketplace. Good for account-level overviews.
- Pass profile_id: filters to one advertising profile. Required for all write operations.
To see available profiles, check get_account_info.amazon_ads.enabled_profile_ids.
Date defaults
Most tools accept optional start_date and end_date in YYYY-MM-DD format. When omitted:
- Ads tools: last 30 days.
- Sales summary: last 7 days.
- Inventory: latest available snapshot.
Ranking tools have specific date parameters for each view. See the keyword rank tool reference for details.
Rate limits
- Per key: 120 requests per minute, 7,200 per hour.
- Daily caps: none by default. Only applies to keys with a configured daily limit.
- Live API tools: subject to additional Amazon rate limits. The server handles throttling and retries, but sustained high-frequency calls may see 429 responses.