SYNTHETIC PROOF WALKTHROUGH

Stop a procurement-agent proposal above the approval threshold

A synthetic policy preflight that returns explicit approval evidence before a separate procurement connector acts.

See the three stepsRead the product contract →
NO KEY · NO UPLOAD · NO CUSTOMER DATAThis demonstration runs entirely in your browser using the visible synthetic fixture below.

THREE STEPS

Put the control before the consequential action.

The proposed 1,000.00 USD purchase order exceeds the supplied 500.00 USD approval threshold with no recorded approval.

  1. 01

    Supply the proposed action

    The caller provides agent, action, amount, budget, authority, vendor, contract, approval, and category policy evidence.

  2. 02

    Evaluate explicit rules

    The preflight checks allowed action, restricted category, budget, requester authority, vendor, contract, and approval threshold.

  3. 03

    Hold before invocation

    Missing approval returns REVIEW_REQUIRED before the customer invokes its own procurement system.

VISIBLE SYNTHETIC CONTRACT

Inspect exactly what the workflow sees.

The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.

Customer-authorized input
{
  "agent_id": "buyer-agent-1",
  "action": "CREATE_PURCHASE_ORDER",
  "vendor_reference": "northstar",
  "category": "supplies",
  "amount": "1000.00",
  "budget_available": true,
  "requester_authorized": true,
  "vendor_approved": true,
  "contract_reference": "MSA-2201",
  "approval_required_above": "500.00",
  "approval_present": false
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "PROCUREMENT_APPROVAL_MISSING",
      "severity": "HIGH",
      "message": "The amount meets the supplied approval threshold without recorded approval.",
      "evidence": {
        "amount": "1000.00",
        "approval_required_above": "500.00"
      }
    }
  ],
  "evidence": {
    "agent_id": "buyer-agent-1",
    "proposed_action": "CREATE_PURCHASE_ORDER",
    "amount": "1000.00",
    "category": "supplies"
  },
  "next_action": "Obtain the required approval before the downstream workflow continues."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

Procurement Agent Safety does not authorize an agent, connect to procurement software, create a PO, change a vendor, reserve budget, or release payment.

Decision
REVIEW_REQUIRED
Named exception
PROCUREMENT_APPROVAL_MISSING
Evidence
amount1000.00approval required above500.00
Next action
Obtain the required approval before the downstream workflow continues.

KEEP BUILDING

Move from the synthetic fixture to the exact API contract.

Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.

Product contract →Implementation guide →Security posture →

Try the control through the supported buyer path.

RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.

Get an API key on RapidAPIExplore every synthetic demo →