One set of endpoints

SellerSheet has one set of tools — more than 400 of them. They reach you three ways, each with its own job:

1. An MCP tool your AI calls in a conversation — through https://sellersheetai.com/mcp. This is where the work happens: your agent reads, decides, asks you, and acts. Connect an AI client.
2. A Tool API operation your own code calls — POST https://api.sellersheetai.com/api/v1/tools/{tool}. A dashboard or approval page your agent builds on it is live: its numbers update and its buttons act on Amazon. Early access — Call from code.
3. The engine behind the Google Sheets add-on, where your team does bulk edits and keeps the record. See the add-on docs.

Over MCP and the Tool API a tool keeps its name, its arguments and its result, so a call your agent made in chat, your code can make tomorrow (the add-on drives the same operations from your sheet rows):

{
  "name": "orders_searchOrders",
  "arguments": {
    "store": "myStore-US",
    "created_after": "2026-10-01T00:00:00Z"
  }
}

curl -X POST https://api.sellersheetai.com/api/v1/tools/orders_searchOrders \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"store":"myStore-US","created_after":"2026-10-01T00:00:00Z"}'

What every call sharesCopy Anchor Link

• One store argument. Store-scoped tools take store, a ref such as myStore-US from get_user_context — Store refs.
• One result shape. notification, data, human_action — Responses & errors.
• One way to page. A token in, a token out; your agent or your loop calls again — Paging.
• One label per tool. Read, write or destructive, and write access per store — Read, write & destructive.
• The vendor's own names. A tool that wraps one Amazon operation carries Amazon's name, such as orders_getOrder or fbaInbound_listPlacementOptions; a SellerSheet workflow over several operations keeps the API area's prefix with a lower-case tail, such as fbaInbound_create_sta_sheet.
• The schema says the rules. Allowed values, bounds and formats from Amazon's specification are in each tool's input schema, so a wrong value is refused before anything reaches Amazon.

Where to go nextCopy Anchor Link

• Workflows — one page per job, FBA first.
• Tool reference — every tool, its arguments and a ready call.