Product / Try a quote
What an agent sees when it asks about your pricing.
A buyer agent asks North Star Compute for a quote. Every number comes from the seller's published rules, not generated text.
No quote
BlockedThis agent key is over its daily quote value limit, so Atlas refuses the request instead of quoting it. The agent is told to back off and retry later; it never learns the limit.
Seller rule: up to $25,000.00 of quotes a day per agent key.
Quoting…
Computing this request against catalog v42.
Request and response
The same quote as JSON over REST, MCP, A2A, UCP, ACP and UAP. Pick a protocol: the request changes, the price does not.
// Request
{
"offerId": "gpu.a100-80gb",
"units": 500,
"region": "US",
"input": { "egressGb": 2000 }
}
// Response 201 Created, main fields
{
"answerType": "indicative",
"binding": false,
"catalogVersionId": "catv_v42",
"data": {
"quoteRequest": {
"id": "q_7f3a",
"offerId": "gpu.a100-80gb",
"status": "indicative",
"calculation": {
"currency": "USD",
"total": "950.50"
}
}
},
"nextActions": [{ "type": "quote.execute" }]
}
What every quote promises
The same order always gets the same price
Same request and catalog version, same quote, every time.
A price range the agent can't go outside
Every quote carries a minimum and maximum the seller approved.
Approved by a person above the limit
Over the seller's threshold, someone on their team signs off before anything is agreed.