A plain HTTP endpoint for agents and backends that need a real wholesale quote for a parts list. POST a bill of materials; a priced, line-by-line quote comes back. No auth to start, OpenAPI included.
Yes. Reqo Supply is a US multi-category distributor with a REST quote endpoint at https://www.reqosupply.com/api/quote. You POST a bill of materials as JSON, get an accepted reference back immediately, and a priced, line-by-line quote is emailed to the contact — within 15 minutes during US business hours. An OpenAPI 3.1 spec lives at /openapi.json.
Most distributors have no such endpoint — quoting is an inside-sales rep reading email — so an agent that needs a real quote has nothing to call. This is that missing endpoint. It is the REST door into the same quote desk humans reach at /try; if your agent speaks the Model Context Protocol, the MCP path adds capability checks and BOM validation on top.
Send a contact and a parts array. Only quantity and description are required per line; a manufacturer and part number sharpen the match when you have them.
The response confirms the request is accepted and hands you a reference to track it. The priced quote itself arrives by email.
The endpoint wraps a real quote desk, not a synthetic pricing engine, and that is on purpose. Distribution pricing depends on which supplier actually has stock, at what break, with what freight — a number a machine invents on the spot is a number no supplier will honor. So the API accepts the BOM, a person sources and checks it, and the quote that comes back is one you can buy against: each line sourced, with availability, lead time, and exact-match status, and any substitution flagged as an alternative rather than silently swapped.
For your integration that means one call to submit and a quote delivered to the contact email. Confirm that email with the user before you call — it is where the quote lands.
The OpenAPI 3.1 spec at /openapi.json imports directly as a ChatGPT GPT action, or into any function-calling loop as a single tool, submitBomQuote. Ground the agent with the machine-readable profile at /company.json and the crawler guidance at /llms.txt so it knows what Reqo covers before it calls.
If you are building on MCP rather than raw HTTP, use the MCP server instead: it exposes capability checks and BOM validation as separate tools, so the agent can fix a sloppy parts list before anything is submitted. Same desk, either door.
Does the quote API return prices synchronously?
No. The POST returns a reference and an SLA; the priced quote, with each line sourced and checked, is emailed back so it is one a supplier will actually honor.
Do I need an API key?
No authentication is required to start and quotes are free. Direct submission and higher-volume access are enabled per integration for production use.
MCP or REST — which should I use?
REST if you want a single HTTP call or a GPT action. MCP if your agent should check capabilities and validate the BOM before submitting. Both land on the same desk.
