Axiom

Sends the user's answer to a question Axiom asked about an order, and continues that order. Use this only after place_order or get_order_status returned status="needs_answer". Pass that orderID and questionID plus the user's choice: selectedOptionID from options, free-text userInput when allowFreeText is true, or both. Do not use this for status="needs_clarification" or "unavailable" from place_order: no order exists yet, so ask the user and call place_order again instead.

answer_order_question

Returns where an order stands, by the orderID from place_order or list_orders: status, a ready-to-relay userMessage, the approvalLink or question when Axiom is waiting on the user, and the receipt once the store has confirmed the order. Answers immediately. Use this only when the user asks about an order. Axiom emails the user for approval, questions, and the result, so do not check on a schedule. Only status="completed" means the order went through. If status="awaiting_approval": send the approvalLink. If status="needs_answer": ask the question, then call answer_order_question.

get_order_status

Returns the card on file (brand and last 4 digits only) and whether the user has finished the account setup required to order: verified email, linked card, phone number, and shipping address. Use this when the user asks which card Axiom has on file or whether their account is ready. It is optional before an order: place_order performs the same checks and reports the card that will be charged. If accountSetupComplete=false, relay userMessage and setupUrl and do not call place_order until the user says setup is done.

get_payment_method

Lists the user's recent orders, most recent first, each with its orderID, store, total, status, and orderUrl. Only status="completed" means an order went through. Use this when the user asks about their orders, or to find the orderID of an order to check with get_order_status.

list_orders

Places a real order. Axiom checks the request, then buys the item at the store with the user's saved card. Returns within about 25 seconds with an orderID; the order finishes in the background and Axiom emails the user the result. Use this when the user clearly asked to buy something AND you can state: (a) the store and its https URL, (b) the specific product, and (c) every variant that product type requires: size and width for shoes and apparel, storage and color for electronics, flavor, size, and count for food and drink, loft and grind for golf clubs, and so on. Resolve these from the user's words, earlier turns, or memory. Never invent them. Do not use when any of (a), (b), or (c) is unknown or ambiguous. Ask the user first: every call counts toward the user's limits, and repeated attempts get blocked. Do not use for browsing, price checks, or hypotheticals, and do not call again after mandate_denied, limit_reached, or account_setup_required. Pre-flight checklist: store and URL known; exact product known; required variants known; the user actually asked to buy. Any box unchecked: ask the user, then call. Responses carry status, nextAction, userMessage (relay to the user as written), and agentInstructions (for you). in_progress: relay userMessage and stop. needs_answer: ask the question, then call answer_order_question. needs_clarification or unavailable: ask the user, then call place_order again (no order exists yet). Only status="completed" means the order went through.

place_order