TXRISK

Services

Sellable x402 lanes built around buyer-safe proof.

TXRISK packages one public proof path per lane so buyers can validate a paid control point quickly. Lane 1 is the agent payment policy gate on POST /v1/action/authorize, shipped with a 10-minute evaluator and four action templates.

Lane 1

Agent Payment Policy API

What the buyer runs

One browser-safe evaluator against POST /v1/action/authorize with native x402 payment recovery handled automatically.

  • Templates: treasury transfer, vendor payout, subscription purchase, browser checkout.
  • Decisions: allow, review, deny.
  • Outputs: policy reasons, operator step, billing proof.

What the seller forwards

Docs, playground, and the partner evaluator pack now point to the same compact lane so CEO or CMO can send one entry link instead of a mixed engineering packet.

  • Partner pack: /partner-evaluator.html
  • Docs: /docs/
  • Playground: /playground.html
  • Contract: POST /v1/action/authorize

What We Deliver

Service lines

Wave-1 Route Delivery

Contract hardening, validation rules, and deterministic response handling for the shipped Wave-1 routes: `POST /v1/wallet/risk-snapshot`, `POST /v1/webhook/verify`, `POST /v1/lead/qualify`, and `POST /v1/action/authorize`.

x402 Billing Enforcement

Public `402 payment_required` handling, request-level billing artifacts, bounded connector access through the remote MCP wrapper, and fallback operator billing flows for safe monetization.

Onboarding Operations

No-call intake packets, dry-run scenarios, and partner handoff motions that reduce activation friction.

Readiness + Reliability

SLO-oriented telemetry baselines, rollout checkpoints, and daily KPI update discipline during beta windows.

Partner Intake

Forward one evaluator bundle instead of stitching your own

What the partner sees first

The bundle leads with the fastest review order: action authorization, discovery metadata, remote MCP metadata, then supporting routes.

  • Live review page: /partner-evaluator.html
  • Best first route: POST /v1/action/authorize
  • Live metadata: /discovery/resources and /.well-known/mcp/server.json

What this removes

No custom route walkthrough, no manual proof assembly, and no guessing about which transport is direct x402 versus MCP header-auth.

Open partner evaluator pack

Delivery Motion

Typical engagement timeline

  1. Day 1: technical intake and integration scoping
  2. Day 2: sandbox issuance and billing test path
  3. Day 3: readiness run with success/402/recovery checks
  4. Day 4+: live partner onboarding and KPI tracking

Launch Planner

Turn rough demand into a starter package

Estimate the first month credit target, support motion, and launch brief before you send intake.

Before you send intake

Shape the commercial brief with concrete launch inputs

This left rail is meant to do real pre-sales work, not just hold form controls. Set the workflow, demand level, and support model first so the package recommendation on the right stays grounded.

  • Match starter credit to projected paid request volume.
  • Choose the first route and evaluator sequence for launch review.
  • Generate an email-ready brief for onboarding, ops, or procurement.

Recommended starter package

Pilot Starter

Sized for teams validating one production flow before expanding volume.

36.00 USDC Estimated first-month spend
45.00 USDC Suggested starter credit
< 24h Target setup window
/v1/wallet/risk-snapshot Recommended first route
  • Loading package recommendations...

Evaluator sequence

Success call, low-balance 402 check, then recovery retry.

  • Loading evaluator outputs...
Email this launch plan

This launch note is formatted for the onboarding desk and partner DMs.