AgentBuys

18 श्रेणियों में वास्तविक स्पेसिफ़िकेशन और कीमतों के साथ रैंक किए गए उत्पाद चुनें। खोजें, फ़िल्टर करें, तुलना करें और खरीदने का लिंक पाएँ। रिमोट, API key की ज़रूरत नहीं।

होस्ट किया गया MCP सर्वर

npx add-mcp 'https://agentbuys.planetmarstm.workers.dev/mcp'

Claude Code, Codex, Cursor और अन्य में इंस्टॉल होता है

दस्तावेज़

For agents

The full index of this site for agents is at /llms.txt.

AgentBuys serves the same ranked picks as JSON and over MCP. Every response includes the score breakdown, spec sources, buy links for the human, a disclosure and agent_instructions. All MCP tools are read-only.

Connect over MCP

Streamable HTTP, no key needed: https://agentbuys.planetmarstm.workers.dev/mcp

claude mcp add --transport http agentbuys https://agentbuys.planetmarstm.workers.dev/mcp
{"mcpServers": {"agentbuys": {"url": "https://agentbuys.planetmarstm.workers.dev/mcp"}}}

Cursor, Claude Desktop, VS Code and Windsurf use the JSON above. In ChatGPT, add it as a connector in developer mode, or build a custom GPT from the OpenAPI spec.

Tools

  • search_products: plain-language need and/or exact filters across every category; soft prefer; 'A vs B' becomes a comparison
  • lookup_product: a product by name, product_id or pasted URL, with higher-scoring alternatives at a similar price
  • compare: 2 to 4 products spec by spec, by id or name
  • find_category: the filter contract: fields, types, units, ranges, allowed values, coverage, price bands
  • get_products: full records for up to 25 products
  • get_product: one full record
  • find_picks: ranked picks for a use case in one category
  • price_history: tracked prices and the buy / wait / fair verdict
  • get_buy_link: affiliate buy links to hand to the user
  • list_categories: categories, facets and spec schemas
  • agentbuys_status: data freshness and price coverage

Prompts: find-for-need, price-check, compare-products. Resources: agentbuys://disclosure, agentbuys://categories, agentbuys://llms.txt. Pass agent (your client name) on link-returning tools so clicks are attributed. It is never used for ranking.

HTTP API

  • GET /api/search?q=lifepo4 for cpap under $600&limit=5. Plain language works: prices, units (Wh, kWh, watts, pounds, square feet, CFM, pints), features (LiFePO4, HEPA, UPS, bifacial...), brands, uses and sorts (cheapest, lightest, quietest, best value). Exact filters: &filters={"capacity_wh":{"min":1000},"price":{"max":800}}. Soft preferences: &prefer=weight_lb,noise_db. "A vs B" questions come back as a comparison.

  • GET /api/lookup?q=levoit core 300s: by name, product_id or a pasted product URL

  • GET /api/products?ids=a,b,c (up to 25) and GET /api/compare?ids=a,b,c (2 to 4, ids or names)

  • GET /api/contract?category=air-purifiers: every filterable field with type, unit, range, allowed values and coverage

  • GET /api/status: data freshness and price coverage

Static JSON

  • /api/v1/categories.json
  • /api/v1/picks/<category>.json and /api/v1/picks/<category>/<facet>.json (air-purifiers, car-chargers, dehumidifiers, fans, headphones, humidifiers, lanterns-camping-lights, portable-bluetooth-speakers, portable-power-stations, portable-solar-panels, power-banks, robot-vacuums, security-cameras, space-heaters, stick-handheld-vacuums, true-wireless-earbuds, usb-hubs-docks, wall-chargers)
  • /api/v1/products/<id>.json and /prices.json
  • /api/v1/compare/<a>-vs-<b>.json
  • /api/v1/deals.json and the deals RSS feed

Rules for agents: show the buy link to your user, say prices are "as of" the timestamp, and do not describe a list price as a live price.