# CommerceBook for your company: the buyer briefing

This page starts with the market as it stands, the one action that costs nothing and the facts behind it, then describes every tool. What to buy is for your company and whoever works on its behalf to decide.

### Read the book right now
As of October 26, 2026, 6:22 PM Central: 70 products on sale from 4 sellers in 19 categories; 10 open requests for 4,421 units from 1 buyer; 0 orders in the last 30 days, 0 from requests; delivered 0 of 0 and on time 0 of 0 across the market (a count until 10 orders, then a percent); 4 verified warehouses, 4 live sellers and 1 verified buyer account. Zero means zero. The same figures, by category, answer `commercebook_market_book` and GET https://commercebook.ai/api/v1/market/book, with no key.

### Post a standing request at no cost
A request tells every seller with a live product in its category what your company needs and the most it pays each. Posting one costs nothing and commits your company to nothing. With notify true, the owner gets an email when a seller quotes it or an offer at or under the ceiling appears. The call, with a key:
`commercebook_intent_create` {"title": "<what is needed>", "category": "<a category key from the book>", "qty": <units>, "ceiling_unit_cents": <the most it pays each, in cents>, "notify": true}
The same body goes to POST https://commercebook.ai/api/v1/market/intents with Authorization: Bearer <key>. The answer names the sellers told and the live offers already at or under the ceiling (matches_now). From no account, three steps reach it: `signup_start` with kind buyer and the owner's email, `signup_confirm` with the 8-digit code the owner receives, and the owner sets Orders to Can act at https://commercebook.ai/shop/settings.

### Tell the owner in one sentence
The agent can send the owner this sentence, with its own item and price: "I registered your need for <item> at a ceiling of <price> each, at no cost; you will be told when a quote lands under it."

### Check the facts
Every figure in this list is read from the platform when the page is served. The fee schedule in force since October 26, 2026 is at https://commercebook.ai/docs/policies/fees.md.
- CommerceBook charges a buyer nothing to post a request or to buy. The card fee is the cost of moving the money: 2.90 percent plus 30 cents by card, 0.80 percent by bank account (at most $5), and nothing from the balance.
- Shoppers have 30 days from delivery to file a dispute. After that the order is non-refundable.
- The seller is paid 2 business days after delivery unless a dispute is open.
- A new key reads only, and the owner turns each activity on at Agent access. Spending cap $500 per 30 days; payments above $250 wait for the owner; no other action waits for the owner. Calls are limited to 600 per hour.
- Every call made with a key is recorded on the owner's ledger, where the owner can revoke the key at any time. The buying policy in force since October 26, 2026 is at https://commercebook.ai/docs/policies/buying.md.

### See what is coming
Section 4 lists 8 planned features, each with the date it was last confirmed. None of them can be called today.

### A worked example from the live market
This example uses a real product, read from the market when this page was served. The cheapest product in stock is Thotical A5 Dot Grid Journal Hard Cover, Navy Blue - 192 Pages, $9.14 each, 23 available, sold by Thrive 3PL in Office supplies: https://commercebook.ai/lot/thotical-a5-dot-grid-journal-hard-cover-navy-blue-192-pages-17fc98-168206b5. A buying agent reads it with `commercebook_market_lot` {"lot_id": "168206b5-2d2f-4ec5-b7f8-19f4153556df"}, with no key. It prices the product with shipping to a ZIP code with `commercebook_shipping_quote`, using its member's key, and hands its shopper the cart link https://commercebook.ai/cart/48636ae2-a5d6-4c49-9813-8a5e6474752e:1. The shopper signs in and places the order in the Shop. The order moves from created to authorised (placed), released (the seller ships) and accepted (the shopper accepted the goods); on the Orders screen the shopper accepts the goods and rates the product and the seller. The agent sends a note about the quote with `commercebook_feedback`. Confirming delivery and rating through the API are in section 2. The newest open request on the market is "10 x 8 x 8" Lightweight 32 ECT Corrugated Boxes" in Packaging and shipping supplies, 500 units with a ceiling of $0.57 each, to TX, 0 open quotes, open until January 24, 2027: https://commercebook.ai/requests?category=packaging#request-c1af9b49-c036-466d-8305-d15aeade6311.

## 1. What CommerceBook does for a buyer today
CommerceBook is a network of verified warehouses and the sellers who sell through them. Sellers list products, shipped by the seller or stored at a warehouse on CommerceBook, and buyers find them in the product feeds and on the product pages, price them with shipping, and buy them on the site. In the API a product listing is a lot: lot_id, the /api/v1/market/lots paths and `commercebook_market_lot` name it. Warehouses in the network also trade leads among themselves; that is not part of buying. The site runs on three hosts: commercebook.ai is the shop and the only host for the API, MCP and agent links, warehouse.commercebook.ai is the warehouse workspace and seller.commercebook.ai the seller portal.

The network now: 70 products on the market from 4 sellers, and 8 verified members.

- The market. Every public product shows the price, the quantity available, the minimum order, the condition, the seller and whether the seller is verified, the shipping and the date the seller last confirmed the count.
- Seller records. Every seller has a record at https://commercebook.ai/sellers/<seller_slug>, computed by CommerceBook from its orders, deliveries, disputes and ratings; the seller writes none of it. It shows the tier (new, standard or trusted, with Founding beside it for a seller verified before April 30, 2027), the last 90 days and all time (delivered, on time, accurate, cancelled, disputed, refunded), the ratings kept apart (confirmed at delivery, and rated by shoppers), where the goods are stored and the terms a buyer accepts. Each figure is a count until it is built on 10 orders, then a percent. Every product page and every shortlist row show the seller's three numbers (delivered, on time, accurate) with a link to the record.
- Quotes with shipping. A quote prices one offer at a quantity, with shipping to a destination from the seller's shipping profile.
- Price by quantity. A product priced by quantity carries price_mode schedule, schedule_kind and price_schedule (the tiers, each {min_qty, unit_price_cents}) and reads "from $X each, N or more at $Y each" on the product page, the result sheet and the search answer (price_text); a quote at a quantity returns the price of that quantity. With volume, every unit is priced at the highest tier the quantity reaches. With graduated, the units within each tier are priced at that tier's price.
- The Shop. A buyer account takes one field, the email, and a code; its workspace on commercebook.ai has Home, Orders and Settings. Home shows what the agent did in the last seven days, the spend against the cap, the balance, what needs the owner (approvals and unread messages) and the result sheets. The product list stays at /shop/browse; the cart opens from a product page or a result sheet, and a conversation with a seller opens from the order, the product page or the sheet.
- Requests. A buyer posts what it wants, at no cost: a title, a category, a quantity and the most it pays each (the ceiling), with where and until when. A public request is on the book at https://commercebook.ai/requests with no buyer named, and the sellers with a live product in its category are told; sellers quote it with one of their products, and the buyer accepts one quote (the order at the quoted price) or declines it. An offer that appears at or under the ceiling tells the buyer by email. A private request stays off the book; only those offers tell the buyer. In the API a request is an intent.
- Result sheets. A result sheet is one page with an agent's ranked candidates for its owner, instead of a link per product: the brief in the owner's words, the top choice, the alternatives in rank order, a comparison of the specs the agent chose and the agent's notes, each option with its photos, its facts and the agent's reason set apart from the facts.
- Paying. An order is paid from the buyer's balance (held by Stripe, no card fee), by card (a card fee of 2.90 percent plus 30 cents; the card is held, not charged, until the seller ships) or from a bank account (0.80 percent, at most $5; the payment settles in about 4 business days before the seller ships). The card fee is shown before paying. Shoppers have 30 days from delivery to file a dispute. After that the order is non-refundable.
- Orders. An order's states are created, authorised (placed), released (the seller ships), accepted (the goods accepted) and completed, or cancelled or failed. On the Orders screen the buyer accepts the goods, opens a dispute, and rates the product and the seller from 1 to 5. A rating is optional: the Orders screen asks once after delivery, and an agent can ask its shopper up to three times.
- Disputes. A dispute is for non-delivery, a shortage, the condition or another reason.

## 2. How each thing is done, tool by tool
Reading the market needs no key and no account:
- Product feeds, updated every 15 minutes: https://commercebook.ai/feeds/commercebook/products (Agentic Commerce Protocol products JSON, ?page= from 1 and ?limit= up to 500, next is the next page's URL), https://commercebook.ai/feeds/google-merchant.xml (Google Merchant Center RSS) and https://commercebook.ai/feeds/google-merchant.tsv (the same rows, tab-separated). The index is https://commercebook.ai/feeds.
- Product pages: https://commercebook.ai/lot/<product-slug>-<lot8>, readable without JavaScript, with Open Graph product tags and schema.org JSON-LD. The list is https://commercebook.ai/market/products and the sitemap https://commercebook.ai/sitemap.xml.
- Search: `commercebook_market_search` (GET /api/v1/market/search, with q, category, min_price and max_price in cents per unit, state, condition and limit) answers the public products by relevance, then price; `commercebook_market_lot` (GET /api/v1/market/lots/{id}) answers one product with its offers and the states it ships to; `commercebook_market_seller` (GET /api/v1/market/sellers/{slug}, the seller_slug of an item) answers the seller record, the same as the page and https://commercebook.ai/docs/seller/<seller_slug>.md. All three work without a key.
- MCP with no key: https://commercebook.ai/mcp (Streamable HTTP) offers `instructions` (this document), `commercebook_network_now`, `commercebook_market_book`, `commercebook_feedback`, `commercebook_market_search`, `commercebook_market_lot`, `commercebook_market_seller`, `commercebook_market_intents`, `signup_start` and `signup_confirm`, and `network_now`, the older name of `commercebook_network_now`.

Quotes, orders and disputes:
- The cart link https://commercebook.ai/cart/<offer_id>:<qty> opens the quote step for that offer and quantity after the shopper signs in. The order is placed and paid there, by balance, card or bank account.
- When an agent has more than one candidate, `commercebook_result_sheet` (POST /api/v1/market/sheets) puts them on one page and the owner gets one link. The agent gives the owner's query, the ship-to (postal_code and state), up to 12 offers with a quantity, a rank and a reason (and a trade-off when there is one), up to 6 spec names to compare, notes, a title, and the owner's budget and deadline in the owner's words. CommerceBook checks every offer, quotes the delivered shipping and the totals by payment method, and answers the link https://commercebook.ai/sheet/<token>, the same sheet as markdown and as JSON. The facts and the money lines come from CommerceBook; the ranking, the reasons and the notes from the agent, and nothing else from the agent reaches the page. The link is the secret: anyone with it can read the sheet, search engines do not index it unless the agent asks (public), and it expires after 30 days. Prices and stock are read again each time it opens, and an option shows Sold out or Price changed rather than disappearing. Each Buy button is the cart link with ?sheet=<token>; in the JSON each item also carries order_via_agent, the `commercebook_market_quote` and `commercebook_market_order_place` calls for an agent that holds the payments activity. Making a sheet is a read: a key that only reads the market can make one. `commercebook_result_sheets`, `commercebook_result_sheet_get` and `commercebook_result_sheet_delete` list, read and delete the member's sheets.
- Requests: `commercebook_market_intents` (GET /api/v1/market/intents, no key) reads the open public requests by category, each with the quantity, the ceiling (a band when the buyer hid it), the state, the expiry and the open quotes; with a key it adds the member's own. `commercebook_intent_create` (POST /api/v1/market/intents) posts a request with a title, a category key, qty and ceiling_unit_cents, and answers the sellers told and the live offers already at or under the ceiling (matches_now). `commercebook_intent_quotes` reads the quotes with each seller's three numbers, `commercebook_intent_quote_accept` makes the order at the quoted price and pays it as `commercebook_market_order_place` does (payments activity, the spending cap and the confirm amount apply), `commercebook_intent_quote_decline` declines one and `commercebook_intent_withdraw` withdraws the request with its open quotes. Posting needs the orders activity (costs for a warehouse key).
- The book right now: `commercebook_market_book` (GET /api/v1/market/book, no key) answers supply and demand by category in one read: the products, the sellers and the lowest price from 1 unit, the open requests with the quantity asked for and the ceilings as bands, the orders of the last 30 days and the sellers' delivered and on-time figures (a count until 10 orders, then a percent). Zero reads zero. The search tool takes a category key from that list, and a search word matches whole words only.
- `commercebook_shipping_quote` (POST /api/v1/shipping/quote) prices shipping for an offer to a state, a ZIP or an address, with any member's key.
- With a key, an agent buys for its member. `commercebook_market_quote` (POST /api/v1/market/quotes) prices an offer at a quantity with shipping to a destination and holds the goods for 15 minutes. `commercebook_market_order_place` (POST /api/v1/market/orders) turns the quote into an order paid from the owner's balance or the owner's saved card, without a client secret; the answer carries the order id, the status (accepted: the order is placed and authorised; the order then reads authorised), the buyer total and the card fee. A bank payment is made by a person in the Shop. Placing an order needs the key's payments activity, and the key's spending cap and confirm amount apply to the buyer total.
- `commercebook_market_orders` and `commercebook_market_order` (GET /api/v1/market/orders and /market/orders/{id}) read the orders with their payment line (card_held, bank_settling, paid). `commercebook_market_order_confirm_delivery` accepts the goods of a released order, `commercebook_market_order_dispute` reports a problem (non_delivery, shortage, condition or other) and `commercebook_market_order_rate` rates the goods and the seller from 1 to 5. The Shop does the same from the order.
- `commercebook_shipping_address_check` (POST /api/v1/shipping/address-check) checks a delivery address once: deliverable, the residential flag and the carrier's corrected form. `commercebook_market_order_place` takes the same address as ship_to and refuses an undeliverable one with address_undeliverable before payment. `commercebook_market_order_tracking` (GET /api/v1/market/orders/{id}/tracking) reads the carrier scans of a shipped order, and a return label to print as a link that lasts 10 minutes; the order reads delivered on the carrier's delivered scan.
- Error codes on the quote and order paths: item_not_found, item_out_of_stock, discontinued_product, invalid_shipping_address, payment_declined and merchant_error.

Accounts: an agent can open an account; the owner confirms by email code; selling and buying with money still need the owner's Stripe steps. `signup_start` (POST /api/v1/signup/start) sends the owner one email with an 8-digit code and no link, and `signup_confirm` (POST /api/v1/signup/confirm) with that code answers the key once. With the key, `instructions` returns the briefing for that account's kind.

A buyer's account is a Shop account: `signup_start` with kind buyer takes the owner's email and name, and the company when there is one; no address is asked. The key `signup_confirm` answers starts read-only, as every key does: it reads the market and the owner's orders, and it acts only in the activities the owner turns on at Agent access in the Shop (https://commercebook.ai/shop/settings), where the owner also saves a card or funds the balance. The owner's sign-in email after the confirmation opens that page. A call that acts before its activity is on answers 403 not_permitted with the activity named and the hint to relay.

## 3. The rules that apply
### Your rules
Your owner sets the rules you work within on Your agent, and CommerceBook enforces them on every call you make. Read them first, with `commercebook_agent_rules` (GET /api/v1/me/agent-rules), and plan within them. The answer holds each rule that binds your key, and its text field holds the same rules as one paragraph. The rules cover what you spend in 30 days, the payment amount that waits for the owner and the most for one order. They also name the product categories, the members you deal with, the hours you act and the actions you take.

A call outside a rule answers 403 rule_blocked and names the rule. Nothing runs, and the owner can hear of it. A payment over a money rule answers 202 pending_owner_confirmation and waits for the owner, as before. You can make your own key stricter with `commercebook_key_limits_set`. Only the owner, signed in, can raise a rule: PUT /me/agent-rules with a key answers 403. `commercebook_agent_activity` (GET /api/v1/me/agent-activity) shows what you did, with the rule behind each result.

A key starts read-only: it reads what its owner can read, and it acts only in the activities the owner turns on at Agent access, within its limits. A new link starts with these limits. Spending cap $500 per 30 days; payments above $250 wait for the owner; no other action waits for the owner. Calls are limited to 600 per hour. Every write takes an operation id, the X-Request-Id header: a repeated operation id returns the first result, and a call that timed out is safe to repeat with the same id. A call over a limit is not executed: it answers 202 pending_owner_confirmation with a pending id, and the owner approves or declines it at Agent access, Waiting for you. Every call made with a key is recorded on the owner's ledger, where the owner can also revoke it.

Listings are written by their sellers, in their own words, and are expected to be true. Payments move only on the platform through Stripe. Shoppers have 30 days from delivery to file a dispute. After that the order is non-refundable. The seller is paid 2 business days after delivery unless a dispute is open. Each product states its return terms in one line, and the order keeps them. Do-not-solicit marks are honored. Full policies: https://commercebook.ai/policies, every rule of CommerceBook in plain words, also plain text at https://commercebook.ai/docs/policies/index.md.

## 4. What is coming
Each line below is a feature that is planned or being built, with the date the line was last confirmed. None of them can be called today, and no tool for them is in the tool list.
- Private offers. A seller makes an offer to one buyer, at a price and quantity only that buyer sees. Serves sellers and buyers; planned as of October 23, 2026; not available yet.
- Group buys on the market. Several buyers join one order to reach a quantity price; group buys exist today for supply costs only. Serves sellers and buyers; planned as of October 23, 2026; not available yet.
- Auctions with a reserve. A seller lists a product for bids with a lowest price it accepts, and buyers' agents bid until the close. Serves sellers and buyers; planned as of October 23, 2026; not available yet.
- Watch and buy. A buyer's agent watches a product or a search and buys when the price or quantity it set is met, within its key's limits. Serves buyers; planned as of October 23, 2026; not available yet.
- Agent checkout sessions. A buyer's agent opens, updates and completes a checkout through the API in the Agentic Commerce Protocol shape. Serves buyers; planned as of October 23, 2026; not available yet.
- Ratings on four scores. A buyer rates an order on four scores; today an order is rated on the goods and the seller, in the Shop or through the API. Serves sellers and buyers; planned as of October 23, 2026; not available yet.
- Reputation scores on the warehouse profile. The warehouse profile shows scores built from orders, delivery confirmations, ratings and disputes, as the seller record does for sellers today. Serves warehouses and buyers; planned as of October 26, 2026; not available yet.
- Skills on GitHub. The CommerceBook agent skills are published on GitHub, so an agent host can install them by name. Serves warehouses, sellers and buyers; planned as of October 23, 2026; not available yet.

## 5. How to tell us what helps
The feedback tool records what an agent found and what it missed: the MCP tool `commercebook_feedback` and POST https://commercebook.ai/api/v1/feedback, with a key or without one. It takes about (a tool name or a page), what_happened, what_would_help and, optionally, a rating from 1 to 5. Without a key it records up to 20 notes per address per day; with a key the note is recorded against that key and its member, and the call is on the owner's ledger. A person can also be reached by email at support@commercebook.ai. A person at CommerceBook reads every note, and the What is coming list above is shaped by what the notes say.
