API / Interoperability
Six tools, not thirty endpoints. A chatty server makes an agent burn context stitching fragments and gives it room to hallucinate the join.
MCP @commercecensus/mcp
| Name | Type | Notes |
|---|---|---|
| find_product | 1× | Which product is the user talking about? |
| search_commerce | 2× | Intent in, ranked products out. |
| best_price | 4× | Where is it cheapest right now, landed? |
| price_context | 3× | Is this actually a good price? |
| recall | 1× | What do we already know about this shopper? |
| watch_price | 1× + rent | Tell me when it drops below X. |
// claude_desktop_config.json
{ "mcpServers": { "census": {
"command": "npx", "args": ["-y", "@commercecensus/mcp"],
"env": { "CENSUS_KEY": "cc_live_…" } } } }
> is the XM5 a good buy right now?
price_context("sony wh-1000xm5")
→ "excellent" — $198.00 at bestbuy, percentile 4 of 89 days,
low $198.00 / median $319.99 / high $398.00Each tool declares its meter, because no human approves individual agent calls and a metadata lookup should not cost what a live cross-seller compare costs.