Platform
How agentcentral works
agentcentral syncs your Amazon seller data on a daily schedule 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) | 3-day attribution window | Daily |
| Business Reports | ~72 hours | Daily |
| Sales summary | Hours | Daily |
| Orders | Near-real-time | Every 15 minutes |
| Inventory | Daily snapshots | Daily |
| Search Query Performance | Weekly granularity | Weekly |
| Keyword ranks | Daily snapshots | Daily |
| Settlements | Settlement period | Daily |
Ads attribution lag
Amazon attributes ad conversions over a 14-day window. Yesterday's ads data is incomplete — ACOS will appear artificially high because sales haven't been fully attributed. The numbers stabilize after about 3 days.
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 daily rank snapshots with the SQP week containing that 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 |
Campaign states
Campaign state writes support ENABLED, PAUSED, and PROPOSED. ARCHIVED is not available because Amazon's Ads API update endpoint rejects it. To archive, use the dedicated archive tools.
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, query the ads://profiles resource, which returns profile IDs with marketplace labels.
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 ranking 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.