Product Intelligence API
One API.
Complete product intelligence.
Everything Buyary knows about a product — scores, claims, consensus, evidence, tradeoffs, recommendations, comparisons, sentiment, purchase links, and confidence — in one structured response.
What you receive.
Core endpoints.
Full product intelligence for a single product.
Side-by-side synthesis across up to five products.
Resolve natural-language queries to catalog products.
Goal-aware recommendations from stated priorities.
Citations and per-source consensus.
Category structure and coverage.
Example request.
curl -s "https://services.buyary.com/v1/product-intelligence?product_name=AirPods%20Pro%203" \\
-H "Authorization: Bearer YOUR_BUYARY_KEY"Example response.
{
"product_name": "AirPods Pro 3",
"buyary_score": 88,
"confidence": 0.97,
"evidence_count": 34,
"consensus": { "experts": 84, "users": 83, "value": 83 },
"claims": [ { "title": "Active Noise Cancellation", "sources": […] } ],
"strengths": […],
"tradeoffs": […],
"citations": […],
"purchase_links": [ { "retailer": "Amazon", "price": 199.99 } ]
}Coverage, freshness, confidence.
Implementation.
Bearer keys, two endpoints, JSON bodies, no CORS by design — the REST docs cover status codes and the data model field by field. Same keys work over MCP.
Common questions.
What comes back in one response?
A single response can include the composite score and sub-scores, verified claims, per-source consensus, supporting evidence, tradeoffs, pricing with available offers, and resolution details such as match confidence. The exact fields returned are documented in the data model.
What are the rate limits?
During the preview, requests are limited to 120 per minute per key, and a batch of N products counts as N lookups. Published limits may change as the API moves toward general availability.
What does detail=compact change?
The compact detail level omits the long-form prose fields, where most of the response size lives, while keeping the structured data. The overall shape is otherwise the same as the full response.
Is the data the same as MCP?
Yes. MCP and REST access the same underlying Buyary product intelligence and use the same credentials. Protocol-specific wrapping or serialization may differ.