How AI agents can ask businesses
for a quote
Agents can already send emails and fill in forms. A simple, published format for quote requests would leave less to guess on both sides. The idea, what it needs, and where Kavel's draft format fits.
The problem
Today an AI agent that wants a quote for someone has two options. It can write an email, which a person at the supplier must read and retype. Or it can fill in a quote form built for people, guessing which box means what.
Both work. Both leave room for mistakes: a size in the wrong field, a quantity misread, a delivery date lost in a paragraph. The supplier then has to ask, and the buyer waits.
Shopping has protocols. Quoting mostly does not.
Agent standards for shopping have started to appear. OpenAI and Stripe announced the Agentic Commerce Protocol in 2025, for buying inside ChatGPT. Google announced the Universal Commerce Protocol in January 2026, developed with Shopify, Etsy, Wayfair, Target and Walmart. Both are built mainly for shopping: finding products, checking out and what happens after.
Much business buying works differently. The price depends on quantity, specification, delivery and terms, and a person approves the order. That usually starts with a request for quote.
The idea: a published place to send a request
A business publishes one web address where software can send a quote request as structured data. Developers call this an endpoint: an address that accepts data rather than showing a page. Next to it, the business publishes a short description of the fields it accepts.
An agent finds the address, sends the request and gets a simple reply saying it arrived. A person at the business reads it and replies with a quote in the usual way.
Think of it as a quote form for machines. The form for people and the version for machines ask for the same things, so neither side is second best.
What a request needs
- The buyer. Company, contact name, and an email address for the reply.
- Each line. A description, the specification (size, grade, colour or part number), the quantity and the unit.
- Delivery. Where, and by when.
- A reply-by date, if there is one.
- Notes. Anything else the supplier should know.
- A flag saying an agent sent it on a person's behalf.
What it leaves out matters just as much. Prices, card details and binding commitments do not belong in a request.
Principles
- A request is not an order. Sending one commits nobody to anything.
- A person replies. The business decides the price and terms, and a person approves them.
- Plain fields. Description, quantity and unit cover most requests. Extra fields should be optional.
- Easy to find. Linked from the business's contact or quote page, so people and agents find the same thing.
- Honest about data. Say what happens to a request once it arrives, and set limits that keep out spam.
How it relates to existing standards
Formal standards for quote documents already exist. OASIS's Universal Business Language (UBL), for example, includes a Request For Quotation document and a Quotation document for electronic procurement. They are thorough, and they suit organisations with systems built to use them.
A small supplier with an email inbox and a price list needs something much smaller. A simple format can still map onto the bigger standards later, line for line.
An example
Here is the kind of request an agent might send. It is for illustration only. Field names in Kavel's draft format may differ, so see its documentation for the current version.
POST /api/q/[page id]
Content-Type: application/json
{
"agent": true,
"email": "buyer@example.com",
"name": "Sam",
"company": "Example Ltd",
"items": [
{ "description": "Hex bolt M8 x 40mm", "spec": "stainless A2", "quantity": 400, "unit": "pcs" }
],
"deliverTo": "Leeds",
"neededBy": "2026-11-14",
"notes": ""
}
Every value is a plain word or number. A person can read it as easily as a program can.
Kavel's draft format
Kavel's draft format for agent quote requests is documented at /agents/quote-requests/. It is a draft. It may change, and it is not an industry standard. It is published openly, so anyone can read it.
Suppliers can use it today through Kavel's free quote request page. Buyers fill in labelled fields, and agents can send the same request as data. Each request is emailed to the supplier, who replies to the buyer directly. Kavel does not keep a copy.
What this does not do
- It does not make an agent choose you. It only makes asking easier.
- It does not price anything by itself. A person still decides the price.
- It does not replace email. Many buyers will keep writing emails, and that is fine.
- It does not prove who sent the request. Treat each one as you would an email from someone new.
If you want help with the reply, QuoteDesk is a tool Kavel has built that reads a quote request and drafts a reply priced from your own price list. You can try the demo or get started free on your own price list.
Written with AI. Announcements and standards mentioned here were checked against public sources in October 2026.