ROBERT DURAN IV
Sign in ↗
EVIDENCE LATTICEDECISION BOUNDARYPROVENANCE RAILR/IV / SYNTHETIC INTERFACE MODEL
R/IV / DEVELOPER PLATFORM

VERIFY
BEFORE ACT.

Make verification an upstream gate before consequential claims, citations, transactions or external actions.
Public primitives06
Catalog29 operations described
ExecutionPolicy + access gated
00 / PRE-ACTION GATE

When verification fails, the agent stops.

Switch between an adequate and inadequate evidence state to inspect the expected gate behavior.

SIMULATED VERIFICATION RESULT

ALLOW / evidence sufficient

Claim supported within authorized scope. Continue only if every independent execution check also passes.

status: verified next: execution policy check receipt: inspectable
INTERACTIVE SYNTHETIC DEMONSTRATION — NOT A LIVE CUSTOMER CASE OR PRODUCTION EXECUTION R/IV / BESPOKE EXPERIENCE
01 / SIX PUBLIC PRIMITIVES

Composable verification.
With explicit gates.

PRIMITIVE / 01

claim.check

Claim support and contradiction. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

PRIMITIVE / 02

citation.verify

Verify the cited proposition against its source. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

PRIMITIVE / 03

agent.action.verify

Pre-action evidence and authority checks. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

PRIMITIVE / 04

transaction.verify

Validate proposed transactional scope. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

PRIMITIVE / 05

provenance.receipt

Inspect what was checked and its limits. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

PRIMITIVE / 06

evidence.monitor

Track defined evidence states and change. Execution availability depends on authentication, authorization, provider readiness, and production entitlements.

02 / DESIGN PATTERN

One deliberate check.
Before the external effect.

R/IV / EXAMPLE / CONCEPTUAL
// Illustrative integration pattern — not a live executable SDK example
const intent = agent.proposedAction();
const result = await riv.verify({
  action: intent,
  sources: context.sources,
  policy: authority.scope,
  spendLimit: budget.limit
});
if (result.status !== "verified") return stop(result.limitations);
await agent.execute(intent);
await riv.receipt(result);
EXPLANATIONNO FALSE SDK PROMISE

Verification as architecture

An agent first defines intent, evidence, policy and spend boundary. The verification result informs whether to act, stop, or request review. A receipt preserves the reviewed state.

This snippet illustrates the architecture. It is not a claim that the specific JavaScript methods shown are available as a production SDK.

Read integration guide ↗
03 / VERIFIED PRODUCTION BOUNDARY

LIVE CONTRACTS.
EXPLICIT LIMITS.

R/IV registers 29 machine capabilities: 23 released one-time operations and six recurring monitors in limited availability. Payment is operation- and rail-specific. Inspect the live status contract before integration; a catalog entry never grants authority to pay or execute.

RUNTIME

23 released one-time operations

The x402 / Base USDC rail returns a live payment challenge for each released one-time operation. Capability state, inputs, limits and receipt behavior are defined by the live registry.

PAYMENT

MPP Card / Link is available for 15 operations

Fifteen operations meeting the current Card / Link floor are available through MPP. The other eight released one-time operations are x402-only. Recurring monitors are review-gated and are not automated machine subscriptions.

RELEASE SCOPE

Operational availability is not a universal claim

Operation-level release status does not establish independent platform certification, benchmark superiority, universal delivery quality, or authorization beyond the exact request.

DISCLOSURE

Public contract. Private implementation.

Public documentation covers callable interfaces, prerequisites, response boundaries and receipts. Proprietary implementation, credentials, private orchestration, provider controls and unpublished research remain restricted.

04 / PRODUCTION SEQUENCE

Discover. Quote. Authorize.
Execute. Verify.

Use the live catalog first, inspect a no-charge preflight, authorize the exact capability and spend boundary, execute through the protected endpoint, then validate and preserve the signed receipt.

01 / DISCOVER
02 / QUOTE

Inspect route and price without charging

GET /api/v1/preflight?capability_id=citation.verify. Authenticated quotes use POST /api/v1/quote. A quote is not a purchase.

03 / AUTHORIZE

Obtain scoped authority

OAuth authorization metadata ↗. Bind capability, input scope and maximum authorized cost before execution.

04 / EXECUTE

Use only the advertised rail

For machine-paid work, use the released https://pay.robertduraniv.com/x402/execute/{capability_id} route or the MPP route returned by its live catalog. Follow the issued challenge; do not construct headers or infer an unsupported path.

05 / VERIFY

Validate the signed receipt

POST /api/v1/receipts/verify. Preserve the receipt, evidence verdict, action gate, limitations and execution identity with the downstream action.