How to add budget controls to a procurement agent

1. Why this guide matters

Procurement-style agents are where automation and real-world commitments collide most obviously. A single wrong action can hit the wrong vendor or exceed the intended amount.

NORNR gives that agent a clear mandate before it ever reaches the vendor side.

2. Install what you need

npm install @nornr/sdk

This guide uses the hosted NORNR path at https://nornr.com, so you can validate the decision flow without standing up the full local stack first.

3. Create the governed wallet

import { Wallet } from "@nornr/sdk";

const wallet = await Wallet.create({
  owner: "procurement-agent",
  dailyLimit: 250,
  requireApprovalAbove: 100,
  baseUrl: "https://nornr.com",
});

This wallet is the mandate. It sets the budget and review threshold before the framework-specific workflow is allowed to continue.

4. Apply it in the workflow

const decision = await wallet.pay({
  amount: 140,
  to: "approved-vendor",
  purpose: "procurement action",
});

if (decision.status === "approved") {
  await submitPurchaseOrder();
} else {
  console.log("Procurement request held or rejected.", decision);
}

The key pattern stays the same across frameworks: ask NORNR for a decision first, then let the expensive or externally billable step run only if policy says yes.

5. What to expect

• approved means the workflow can continue immediately inside its mandate.
• queued means the request crossed an approval threshold and should wait for review.
• rejected means policy did not allow the action to proceed.

That three-way split is what makes the pattern useful: low-risk work stays fast, higher-risk work becomes reviewable, and clearly out-of-policy work never leaves the workflow.

6. Where to go next

• Hosted quickstart
• Control room
• Guides library