Partner Evaluator Pack

One review bundle for listings, integrations, and technical eval intake.

This page is the sendable TXRISK partner bundle. The shortest live buyer proof today is the hosted Wallet Action Preflight API at https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight at 0.002 USDC on Base. The broader TXRISK direct routes and MCP wrapper remain available for evaluators who need the wider product surface after that hosted proof.

Open hosted proof Open TXRISK playground Open docs

Review Order

What a partner evaluator should review first

Start with the hosted Wallet Action Preflight API on https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight as the shortest live proof.
Confirm the exact commercial framing: 0.002 USDC on Base with the expected 402 -> paid retry -> 200 flow.
Open the browser evaluator on /playground.html only if you also need to validate the broader direct TXRISK routes from the same public site.
Check discovery metadata on /discovery/resources to confirm the public sellable route inventory.
Check MCP metadata on /.well-known/mcp/server.json to confirm the bounded connector wrapper and auth model.
Use /docs/ for the hosted-path quickstart plus the supporting direct routes: wallet risk snapshot, webhook verify, and lead qualify.

Live Links

Everything needed for external technical review

Primary proof path

Wallet Action Preflight API
0.002 USDC on Base
402 -> paid retry -> 200 is the canonical hosted buyer proof
TXRISK browser evaluator
Public docs
POST /v1/action/authorize and POST /v1/account/recovery-authorize are the broader direct-route proofs

Machine-readable metadata

Public discovery
MCP server metadata
MCP server card
POST /mcp for bounded connector calls

Current Surface

What is publicly sellable today

Hosted buyer path

POST https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight
0.002 USDC on Base
402 -> paid retry -> 200
Buyer-safe first proof for Bankr-native transfer and approval gating before sign or submit

Broader direct TXRISK routes

POST /v1/action/authorize
POST /v1/account/recovery-authorize
POST /v1/wallet/risk-snapshot
POST /v1/webhook/verify
POST /v1/lead/qualify

Bounded MCP tools

authorize_action
authorize_account_recovery
risk_snapshot
verify_webhook
qualify_lead
get_support_snapshot

Auth Model

Direct HTTP and MCP use different entry semantics

Direct HTTP

The broader TXRISK direct routes are x402-native. First request without a key. Service returns 402 payment_required. Caller retries the quoted request after settlement verification on the public TXRISK flow.

Remote MCP

The remote MCP wrapper uses static x-api-key header auth and exposes Smithery-friendly metadata for header-based connector setup on /mcp. For Smithery, the intended move is to publish the externally hosted TXRISK URL and let Smithery proxy it, while the broader direct HTTP API remains the canonical TXRISK surface behind the hosted buyer proof.

Exact Proof

Fastest external validation flow

export HOSTED_BANKR_URL="https://x402.bankr.bot/0xc04d0d464752a58b046105b45089d579eaf54036/bankr-preflight"

payload='{
  "action": {
    "kind": "transfer",
    "chain": "base",
    "actor": "0x1111111111111111111111111111111111111111",
    "to": "0x2222222222222222222222222222222222222222",
    "amountUsd": 5400,
    "tokenSymbol": "USDC"
  },
  "requestContext": {
    "intentId": "intent_demo_001",
    "merchantAccountId": "merchant_demo"
  }
}'

payment_required=$(curl -isS -X POST "$HOSTED_BANKR_URL" \
  -H "content-type: application/json" \
  -d "$payload")

printf '%s\n' "$payment_required"

# Expected first response:
# - HTTP 402
# - quoted resource is the same hosted Bankr URL
# - after payment, retry the same URL for the final 200