xAI Publishes Procurement Bot Prompt That Requires Approval for Vendor Messages—and Bars Purchases

xAI has published a system prompt for Haggle Bot, a procurement-focused Grok Bot configured to find savings from live vendor data, research alternatives, and support renewal negotiations. Its most consequential design choice is a split authority model: an operator must approve vendor-facing messages, while the bot is barred from purchases, charges, signatures, subscriptions, and other binding commitments.

The published configuration asks an organization to specify where spend, contracts, usage data, vendor dossiers, and colleagues can be reached. Haggle Bot is then instructed to work from those sources rather than produce broad suggestions to renegotiate major suppliers.

Each recommendation is meant to begin with current annualized spending from live data, a realistic savings estimate and mechanism, a single recommendation, and actions already underway. A lead without a traced dollar figure, a specific savings mechanism, and a reason it can be acted on now must be labeled as incomplete rather than treated as a finding.

The template treats contract timing as the central source of leverage. It tells Haggle Bot to maintain a renewal calendar from billing and contract records, prioritize renewals inside an organization-defined window, and investigate at least three real alternatives before recommending a path.

What the bot must establish before a recommendation

• A savings figure tied to live spend data, plus the mechanism that would create it.
• A current reason to act, such as a renewal window, usage data, or a competing quote.
• Alternative pricing measured against the company’s actual software footprint, with dated figures and switching costs included.

Before it drafts an external message, the bot must show the operator a negotiation plan covering the target, opening anchor, walk-away point, proposed tradeoffs, and responses to a rejection, counteroffer, or silence. The prompt also tells it to avoid disclosing protected internal information, such as usage data, seat counts, timeline urgency, or a decision to renew.

Haggle Bot is instructed to keep a dossier for each vendor containing spending, terms, renewal dates, owners, quotes, and the operator’s decisions. It must record why an operator rejected an approach and avoid repeating that pattern, making the configuration a continuing procurement role rather than a single contract-review prompt.

The procurement template arrives alongside xAI’s description of Grok Bot as a persistent agent with its own identity, memory, runtime, and tools. xAI says such Bots can work beyond a single session, with routines that can start work on a schedule or in response to events. Haggle Bot applies that model to the recurring calendar and record-keeping work around vendor renewals.

xAI illustrates the approach with a weekly technology order that it says fell from $14,629 to $6,143 after Haggle Bot compared same-day competitor prices and drafted a request to an Amazon procurement representative. That 58% reduction is xAI’s own example of the configured workflow, not a general performance result for procurement agents.