TXRISK

Services

Sellable x402 lanes anchored by one live wallet action preflight offer.

TXRISK now leads with the Wallet Action Preflight API at https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight. It charges 0.002 USDC on Base for Bankr transfer and approval checks before sign or submit, while the broader TXRISK routes remain available on txrisk.xyz.

Hosted Offer

Wallet Action Preflight API, sold as one clean paid control point

What the buyer runs

One hosted POST call against the Bankr preflight URL with a Bankr-managed x402 payment step before the final decision body.

  • URL: https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight
  • Launch price suggestion: 0.002 USDC on Base.
  • Inputs: one Bankr transfer or approval action plus optional request context.
  • Outputs: mode=bankr_preflight, normalized action, TXRISK risk output, Bankr decision, and execution outcome.

Why this name wins

Wallet Action Preflight API is the recommended package name. It is specific to the actual live contract and clearer than Approval Roast API.

  • Matches the real surface: both transfers and approvals are supported.
  • Signals where it sits in the buyer flow: before sign or submit.
  • Avoids gimmick drift: Approval Roast API is narrower and less legible to risk and treasury buyers.
  • Keeps the wrapper anchored to the live bankr-preflight route instead of speculative roadmap copy.

One-screen value proposition

Charge for a single pre-execution decision that tells an operator or wallet agent whether to allow, warn, or block a transfer or approval before funds move or approval scope is granted.

  • Best buyer: agent-wallet builders, treasury operators, payout teams, and embedded approval rails.
  • Best first proof: 402 -> paid retry -> 200 on the hosted Bankr route.
  • Supporting direct route: POST /v1/action/authorize on txrisk.xyz.

What the seller forwards

One hosted proof URL plus one supporting docs page, instead of starting buyers on the broader direct-route catalog.

  • Hosted URL: bankr-preflight on x402.bankr.bot
  • Buyer docs: /docs/
  • Partner packet: /partner-evaluator.html
  • Secondary direct route: POST /v1/action/authorize

New non-onchain lane

TXRISK also now ships a support-risk control point for sensitive account recovery actions that have nothing to do with onchain settlement but still need the same request-time allow, review, or deny contract.

  • Direct route: POST /v1/account/recovery-authorize
  • Best buyer: support ops, trust and safety, payout ops, and identity-risk teams.
  • Decision types: password reset, MFA reset, email change, and payout destination change.

Why it matters

This keeps TXRISK anchored to request-time controls instead of chain-only data products. The same monetized decisioning wedge now fits support fraud, account takeover, and payout-redirection risk.

  • Operator output remains deterministic: allow, review, or deny.
  • The endpoint still uses the same x402 billing and retry contract as the rest of the public TXRISK surface.
  • The dashboard now exposes the recovery lane alongside the existing wallet, webhook, and lead routes.

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`, `POST /v1/action/authorize`, and `POST /v1/account/recovery-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 hosted Wallet Action Preflight API first, then the broader direct-route and metadata review order when deeper integration is needed.

  • Live review page: /partner-evaluator.html
  • Best first route: https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight
  • 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.