Integration · Relevance AI

RunOnProof for Relevance AI — documentation index

This directory is the public maintenance source for the RunOnProof Relevance AI integration. It explains how to reproduce a safe development configuration, use it, interpret its output, maintain it, and prepare a truthful public case.

The executable contracts remain one directory above this documentation:

../authoring-manifest.json — authoring source and safety defaults;
../schemas/ — input and normalized output contracts;
../runtime.mjs — deterministic selection and normalization;
../SYSTEM-PROMPT.md — agent instructions;
../fixtures/ and ../demo.mjs — synthetic cases;
../CAPABILITY-MATRIX.md — consumer view of current coverage.

Choose your path

If you have never used Relevance AI, follow these pages in order:

For operators and developers:

For communication and future distribution:

Public evidence state

This repository proves the seven synthetic contract scenarios, including the gb.solution.company_check.v1 quote boundary at 0.04 USDC, with zero production calls and zero payment attempts. It does not publish private workspace evidence or claim a Relevance AI Marketplace listing, endorsement, certification, or partnership.

The five private solutions

The RunOnProof private Relevance AI project contains five solution-level Tools. They are internal building blocks for a human-approved workflow, not public Marketplace products.

Solution	What it answers	Public contract
UK Company Verification	Is this the declared Companies House company, and what is its current legal state?	`POST /v1/gb/solutions/company-check`
UK Supplier Approval	May this supplier enter the onboarding workflow, using scoped Companies House and UK Sanctions List evidence?	`POST /v1/gb/solutions/supplier-approval`
UK Invoice & Payee Verification	Are the caller-provided invoice fields consistent with the company and independently supported payee evidence?	`POST /v1/gb/solutions/invoice-payee-verification`
UK Payment Authorization	May one bounded business payment proceed under the available evidence and policy? This is a decision only; it never executes, signs, transmits, or settles payment.	`POST /v1/gb/solutions/payment-authorization`
UK Vendor Change & Continuous Authorization	May a scoped vendor payee-detail change proceed, and may authorization continue under a fresh challenge and prior authorization? Continuation is bounded, never permanent.	`POST /v1/gb/solutions/vendor-change-continuous-authorization`

Every Tool is private, internally Live, connected to the private demo agent, and configured with Requires approval. Publicly available is off, automatic payment is off, and HTTP 402 always means REVIEW pending separate external authorization. No Relevance AI Marketplace listing is currently published.

UK Supplier Approval remains the primary commercial demonstration. The other solutions show the width of the private portfolio without claiming that the whole United Kingdom programme is complete.

Sources of truth and precedence

When two pages disagree, use this precedence:

production runtime coverage and source health at the time of execution;
canonical RunOnProof catalog, pricing and API contracts;
authoring-manifest.json and JSON schemas in this repository;
this documentation;
screenshots, case copy, and historical reports.

Never infer availability from the presence of a route or an old screenshot. A capability must be currently supported, purchasable when applicable, and healthy enough for the requested decision.

Status vocabulary

Repository implemented: code, schemas, fixtures, prompt, and documentation exist in Git.
Published internally: the Tool or agent is usable inside the RunOnProof Relevance AI project.
Production call: the Tool sends a request to api.runonproof.com.
Marketplace published: a separate public distribution state that has not been reached.

Do not collapse these into one word such as “live.”