RRunOnProof
RunOnProof / Agentic commerce
RunOnProof

One decision. Verifiable evidence.

Before the supplier payment.

RunOnProof provides a signed, federal-only decision before a US supplier payment and a separate free technical Agent ID. Payment Decision costs 0.79 USDC per assessment; Agent ID supports local Ed25519 signing and public verification through a free bootstrap. RunOnProof never executes supplier payments.

What your 0.79 USDC buys.

One structured decision about one supplier-payment operation, the necessary checks within supported federal scope, reasons, conditions, remediation, evidence references and the corresponding signed Proof Capsule.

Connect the operation

Bind the supplier, invoice or obligation digest, amount, declared payee, destination and signed buyer mandate to the same request.

Identify a mismatch

Apply the supported policy and mandate limits, evaluate federal evidence and flag a difference between the declared payee and destination.

Inspect the evidence

Retain the reasons, validity, evidence references and signed proof for that specific operation. Recover the acquired result without buying it again.

Prepare the complete operation.

Supply your agent and key, buyer context and signed BuyerPaymentMandate, supplier identity and supported federal identifiers, invoice/obligation reference and document digest, amount and currency, payee and destination references/fingerprints, payment-instruction digest, economic purpose, policy, freshness, disclosure, evidence references, correlation, payment exposure and valuation basis. Keep private keys local. Use the current input schema for exact required fields.

Examples and their limits.

The existing synthetic request illustrates the input structure. It is SYNTHETIC_NOT_EXECUTABLE: placeholder signatures, identifiers and fixed dates are not current authority, a receipt or production evidence.

These are explanations of supported boundaries, not fabricated API responses or newly signed example proofs.

Before paying: common questions.

Is HOLD free?

Not necessarily. A conservative HOLD can be a successfully delivered paid decision. HOLD and UNDETERMINED are not payment permission. Read machine_action, reasons, conditions and validity; no universal refund is promised.

What if the response is lost?

Preserve the exact original request and idempotency information. Use the authenticated recovery contract without paying again for the acquired result. Changed business inputs are not a replay.

How do I verify delivery?

Verify the Proof Capsule signature with the published keys and check its request/evidence bindings and validity. A valid signature does not independently establish the truth of buyer assertions.

Does Virtuals use the same purchase flow?

Use the existing ACP guide for native job authorization, one 0.79 USDC funding and recovery of that job. Do not add an x402 payment. PROCEED, HOLD, REVIEW and RETRY are channel presentation labels; inspect the embedded canonical decision. HOLD/REVIEW are not supplier-payment permission. The published ACP delivery SLA is 15 minutes.

A complete agent journey.

  1. Read the canonical contract and create a free agent identity.
  2. Register a self-service decision purchaser with a signed agent key, payer address, declared organization and bounded fee budget. No external business certification is needed to buy the decision; organization and representation remain unverified. Verified enterprise delegation remains a separate option.
  3. Call the free contact and eligibility APIs to resolve missing inputs.
  4. Verify price, Base, official USDC, receiver and your budget before paying once.
  5. Verify the signed Proof Capsule. Recover the same operation with an owner signature after a lost response; never pay again to recover.

An active agent key, authenticated wallet and authorized funds are buyer prerequisites. Self-service results do not establish enterprise representation or authorize the supplier transfer.

What the decision means.

ALLOW, ALLOW_WITH_CONDITIONS, HOLD, BLOCK or UNDETERMINED, with reasons and evidence. A conservative HOLD can be a successfully delivered decision.

No state good standing, bank-account ownership proof or invoice economic authenticity guarantee. RunOnProof never executes the supplier transfer: payment_executed=false. No customer subscription or continuous monitoring is started.

Contracts and free contact.

Always construct requests from the canonical schema. Marketplace parameter summaries can omit required markers.

POST /v1/us/decision-gates/release-payment-to-supplier/contact
Content-Type: application/json

{"intent":"RELEASE_PAYMENT_TO_SUPPLIER"}

Then POST a complete signed request to /v1/us/decision-gates/release-payment-to-supplier/eligibility. No payment header belongs on contact, eligibility or signed recovery.