TXRISK Launch System
Public proof in front. Paid API operations behind the operator shell.
TXRISK keeps docs, proof, and intake public while the operator shell handles live wallet-paid requests. The current outward-facing contract is the live route set: wallet risk snapshot, webhook verification, lead qualification, and action authorization, plus a bounded remote MCP wrapper for connector clients.
- 34/34 contract checks passing
- 3 partner tracks ready for onboarding
- <24h sandbox setup target after intake
Core Services
What TXRISK helps teams launch first
Wallet and treasury screening
Score wallets before payouts, treasury movements, or partner activation so operators can stop obvious risk before funds move.
Webhook and inbound event verification
Validate incoming events, reject tampered payloads, and keep payment or onboarding flows tied to a clear verification policy.
Paid lead qualification
Route higher-intent submissions through a billable qualification step instead of sending every lead straight to manual review.
Operator launch support
Start with docs and a browser playground, then move into the paid shell for live request runs, billing checks, and retry proof.
Evaluation Path
Use the pages below based on where you are in the buying cycle
Partner evaluator pack
Use one forwardable page when a listing partner or technical reviewer needs the route inventory, discovery links, MCP metadata, and first proof path.
Go to partner packDocs + Quickstart
Start here if you want route definitions, curl examples, headers, the remote MCP entry points, and the shortest path to a first successful paid request.
Go to docsServices page
Use this when you need the commercial view: service lines, onboarding motion, support model, and launch-planning inputs.
Go to servicesDashboard
Open the operator surface when you want one working console for paid requests, billing state, and request inspection.
Go to dashboardPlayground
Test the browser flow, inspect success and `402` behavior, and see how the retry path works before deeper integration.
Go to playgroundCall To Action
Build the intake brief before you email us
- Describe the launch use case, volume, and preferred rail.
- Copy the generated intake brief into email or DM.
- Receive sandbox endpoint and prepaid credit setup within 24 hours.
Generated intake brief
Copy this brief into email or DM. It gives us enough context to return the right starter pack without a scheduling step.
Starter pack target: same-day reply with docs, key, and first route.