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.
Live shape of a call
POST /categorizations
store_id "amazon.com"
description "Waterproof hiking boots, Vibram sole, men's size 44"
- L1Clothing, Shoes & Jewelry412 tok
- L2Men386 tok
- L3Shoes331 tok
- L4Hiking Boots104 tok
1 233 of 4 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.
-
STEP 01
Start at the roots
The store's top-level categories are loaded from the taxonomy and offered as the only options.
-
STEP 02
Pick, then descend
The chosen node's children become the next set of options. Repeat while children remain.
-
STEP 03
Stop on the budget
Every call's tokens are counted. At 4 000 tokens the descent stops and the last match is flagged
truncated. -
STEP 04
Return the whole path
One entry per level, with the store's own category id — remapped to the external code where the marketplace uses one.
Two ways in
Bring a key, or bring a payment.
A request is served if it carries a valid API key or a valid payment. Nothing else is needed — there are no accounts to create, no sessions, no dashboard.
Channel A
API key
Send X-API-Key on every call and get billed after the fact. Usage is recorded per request, priced on input and output tokens separately.
- Header
- X-API-Key: <your key>
- History
- GET /categorizations
- To get a key
- write to us
Channel B
Pay per call — x402
No key, no signup. Call the endpoint, get a 402 with the payment requirements, pay $0.03 in USDC and retry with the signed authorization. Your wallet address is your identity.
- Price
- $0.03 per call
- Network
- Base Sepolia (testnet)
- Header
- PAYMENT-SIGNATURE
- Agents
- MCP tool
payment_info
For agents
MCP server
Point an MCP client at /mcp for three tools: categorize_product, list_stores and payment_info. Keys travel in the same header; payments travel in the request metadata.
- Endpoint
- /mcp
- Free tool
- list_stores
Surface
Two endpoints and a tool call.
| Endpoint | Auth | Returns |
|---|---|---|
| POST /categorizations | API key or payment | The product with one match per level |
| GET /categorizations | API key | Your past categorizations |
| POST /mcp | API key or payment | MCP tools over streamable HTTP |
# categorize one product
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