Public case: an AI agent that stops when the proof is not enough
An AI agent may need to add a supplier, trust a company, or prepare a payment. Before it acts, it needs to know which legal company it is dealing with and what reliable evidence is available.
RunOnProof gives the agent a narrow company decision with the proof and limits attached. The private Relevance AI demonstration has five solution-level Tools: Company Verification, Supplier Approval, Invoice & Payee Verification, Payment Authorization, and Vendor Change & Continuous Authorization.
Supplier Approval is the primary commercial demonstration. The other four Tools show how the same evidence-first boundaries can support company identity, invoice and payee checks, a bounded payment decision, and a controlled vendor-detail change. Payment Authorization only returns a decision; it never executes, signs, transmits, or settles payment.
What the demonstration shows
- The user supplies an exact UK company number.
- The agent selects the smallest suitable RunOnProof check.
- It shows the product and price before a paid action.
- If payment authorization is missing, it returns
REVIEWand stops. - When a result exists, it keeps the evidence, freshness, coverage, and limitations visible.
- It does not turn a source outage or no-match into a promise that everything is safe.
The synthetic payment-required fixture displays gb.solution.company_check.v1 and 0.04 USDC, requires approval, and makes no production verification or payment.
The three answers
PROCEED: the current evidence supports the exact action under the named conditions.REVIEW: a person, missing input, source recovery, evidence, or payment authorization is needed.STOP: the action must not continue.
These are action-specific answers, not a permanent trust score.
What is real and what is synthetic
The public case uses synthetic fixtures for safe, repeatable tests. Synthetic company numbers are not live Companies House results, and this repository exposes no private Relevance AI workspace state.
All five Tools remain private and require human approval. Automatic payment is off. The integration has not been published in the Relevance AI Marketplace and does not imply a partnership, endorsement, or approval by Relevance AI.
Reproduce the case
Developers can run the seven synthetic cases from the RunOnProof repository, then follow the installation guide to recreate the Tool and agent in a private development project. The payment boundary remains closed unless a separate authorized payment client is deliberately introduced.
Short version
RunOnProof helps agents check the company and the evidence before they trust, onboard, or pay. If the proof is incomplete, the source is unavailable, or payment is not authorized, the agent stops instead of guessing.