Protocols

The REST API.

The same service over plain HTTP — for backends, scripts, and stacks where MCP isn’t the integration point. Two endpoints, the same keys as MCP, byte-identical responses.

Single lookup

terminal
curl -s "https://services.buyary.com/v1/product-intelligence?product_name=iPhone%2017%20Pro%20Max" \
  -H "Authorization: Bearer YOUR_BUYARY_KEY"

Add detail=compact for a trimmed body:

terminal
curl -s "https://services.buyary.com/v1/product-intelligence?product_name=iPhone%2017%20Pro%20Max&detail=compact" \
  -H "Authorization: Bearer YOUR_BUYARY_KEY"

Batch

Up to five products per call; results come back in input order.

terminal
curl -s -X POST "https://services.buyary.com/v1/product-intelligence/batch" \
  -H "Authorization: Bearer YOUR_BUYARY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"product_names": ["iPhone 17 Pro Max", "totally unknown gadget"]}'

Status codes

200

The lookup ran — including found: false, which is a 200 with the documented limited-coverage body, not an error.

400

Request validation: missing product_name, an unknown detail value, or a batch outside 1–5 names.

401

Missing, malformed, or revoked key.

429

Throttled — including mid-batch, when a large batch exhausts your remaining rate budget partway through.

Call it from your server, not the browser

Keys are bearer secrets. Keep them in backend code or environment config — a key shipped to a browser is a key you’ve published. The API sends no CORS headers, by design.

Building an agent instead? Connect over MCP →