Market Category Booster
Market Category Booster
Product text in, taxonomy path out

One category is a guess. A path is a listing.

Market Category Booster reads a product description and walks the marketplace's own category tree, level by level, until it runs out of children. You get every node on the way down — the one the listing form actually asks for.

8 taxonomies · REST and MCP · 12 000-token budget per request
Live shape of a call

Follow one request to the leaf.

One description goes in. One node comes back per level, each priced on its own call, until the budget or the tree ends the descent.

POST /categorizations
request
store_id"amazon.com"
description"Waterproof hiking boots, Vibram sole, men's size 44"
path
L1 Clothing, Shoes & Jewelry 412 tok
L2 Men 386 tok
L3 Shoes 331 tok
L4 Hiking Boots 104 tok
1,233 of 12 000 tokens spent · descent ended: no children left
How a request is served

Four levels down, four decisions, one bill.

Each step is a separate model call over the names of a single level — never the whole tree. That keeps prompts small, and it makes the cost of a request something you can read off the response instead of guessing.

  1. 01

    Start at the roots

    The store's top-level categories are loaded from the taxonomy and offered as the only options.

  2. 02

    Pick, then descend

    The chosen node's children become the next set of options. Repeat while children remain.

  3. 03

    Stop on the budget

    Every call's tokens are counted. At 12 000 tokens the descent stops and the last match comes back flagged truncated. A deep tree can't turn into an open-ended bill.

  4. 04

    Return the whole path

    One entry per level, each with the store's own category id — remapped to the external code where the marketplace uses one instead of an internal id.

One way in

One key, and no account to manage.

A request is served if it carries a valid key. Nothing else: no session, no dashboard to log into, and billing settled outside the API.

API key

Send the key in the X-API-Key header. Calls are metered per request and invoiced afterwards — there is nothing to top up and nothing that blocks a call mid-catalog.

Header
X-API-Key
Billing
per request, in arrears
To get a key
write to us

MCP server

Point an MCP client at /mcp for three tools: categorize_product, list_stores and payment_info.

Endpoint
/mcp
Free tool
list_stores
Surface

Two endpoints and a tool call.

Endpoint Auth Returns
POST /categorizations API key The product with one match per level
GET /categorizations API key Your past categorizations
POST /mcp API key MCP tools over streamable HTTP
POST /a2a API key A2A agent, JSON-RPC 1.0 — card at /.well-known/agent-card.json 
# one call, one path back
curl -X POST https://$HOST/categorizations \
  -H 'X-API-Key: <your key>' \
  -H 'Content-Type: application/json' \
  -d '{"store_id":"amazon.com",
       "description":"Waterproof hiking boots, Vibram sole"}'

Descriptions are capped at 2,000 characters: the text is repeated in the prompt at every level, so its length is part of the cost.

Taxonomies

Supported stores.

Pass one of these as store_id. en-US is the Google product taxonomy.

  • amazon.com
  • amazon.it
  • amazon.co.uk
  • ebay.com
  • ebay.it
  • ebay.co.uk
  • shopify.com
  • en-US

Read the reference, send one call.

There's nothing to install. The fastest way to know whether this fits your catalog is to categorize one of your own products.