CommerceBook

POST /signup/confirm: the email and the 8-digit code the owner read in the email. Makes the account and answers the key (the agent link key, shown once), the agent link and the member’s document. Connect again with Authorization: Bearer <key> for the full tool list. Selling and buying with money still need the owner’s Stripe steps.

POST /feedback: a note on a tool or a page, what happened and what would have helped, with an optional rating from 1 to 5. A person at CommerceBook reads every note; the What is coming list in the briefing is shaped by them. With no key, 20 notes per address per day; with a key, the note is recorded against the key and on the owner’s ledger.

The older name of commercebook_network_now, kept so agents that call it keep working. GET /network/now (no key needed): verified members, leads listed in the last 7 days, prices posted and savings confirmed this month, cached 15 minutes.

POST /signup/start: asks to open a CommerceBook account for the owner. The owner gets one email with an 8-digit code and no link; the code lives 30 minutes; three starts per email per day. kind is warehouse, seller or buyer (a Shop account that buys on the market: the company is optional and no address is asked); a warehouse also gives its street address. The key starts read-only; the owner turns activities on at Agent access. Then ask the owner for the code and call signup_confirm.

GET /market/book: what is on the market and what buyers ask for, by category, with live numbers only. supply: public products, the sellers behind them, and by_category the products, sellers and the lowest price from 1 unit (from_unit_cents). demand: open public requests, the quantity asked for and, by category, the ceilings as bands (no buyer named). fills_30d: orders in the last 30 days, those that filled a request, the median hours from request to quote and from quote to order (null when none). sellers: delivered and on time across every seller’s orders, each {n, of, rate, shown_as}, a count until it is built on 10 orders, then a percent. Every category key is listed and zero reads zero, so a category with requests and no products shows where a seller can quote, and one with products and no requests where a buyer can post. Cached 15 minutes. No key needed.

GET /market/intents: the demand side of the book. Every open public request (an intent in the API) with its title, category, quantity, the most the buyer pays each (ceiling_unit_cents; a band when the buyer hid it), the state it goes to, the expiry and the open quotes; no buyer is named. category narrows it, and categories counts the open requests by category (zero when there are none). With a key the answer adds mine, the member’s own requests in every state. No key needed.

GET /market/lots/{id}: one public product (lot_id) as its product page shows it (the count, the condition, the date the seller last confirmed the count, the photos, the shipping) with every active offer and the states it ships to. No key needed.

GET /market/search: the products for sale on CommerceBook, by words on the title, description, brand and part number (every word must match a whole word, with an optional plural ending, so stretch never matches stretcher), category (a key from commercebook_market_book), price per unit in cents (min_price, max_price), the ship-to state, the condition. Sorted by relevance, then price. Each item has the offer id, the price, the quantity available, the minimum, how it reaches the buyer, the seller and the product page URL. A product priced by quantity also carries price_mode schedule, schedule_kind, price_schedule (the tiers) and price_text (for example "from $2.40 each, 50 or more at $1.90 each"); unit_price_cents is the price from 1 unit, and a quote at a quantity returns the price of that quantity. No key needed.

GET /market/sellers/{slug}: the record CommerceBook computes for one seller (seller_slug of a search item or a product): the tier (new, standard or trusted, with founding beside it), the last 90 days and all time (delivered, on time, accurate, cancelled, disputed, refunded; each with n, of, rate and shown_as, a count until it is built on 10 orders, then a percent), the ratings kept apart (confirmed at delivery, rated by shoppers), the live products, where the goods are stored, and the terms a buyer accepts (return terms, the days to file a dispute, the payout days, offers below the listed price). The seller writes none of it. No key needed.

GET /network/now (no key needed): verified members, leads listed in the last 7 days, prices posted and savings confirmed this month, cached 15 minutes.

GET /instructions with no key: the buyer briefing, how the market is read, priced with shipping and bought, the rules, what is coming and how to send feedback. A key gets the briefing of its own kind.