402sentinel.com

Is this payment address safe to pay? DEEP version — deep counterparty assessment: same shape as /api/assess but scans more on-chain settlement history for higher confidence. POST {target:{payto_address}, payment_context?, policy?}. Returns risk_score 0-100, allow/review/block, confidence, per-dimension signals, key_factors and a recommended_policy. Use when the payment is large enough that a thin-data 'review' verdict is not good enough.

RWA risk gate: score a TOKENIZED ASSET (treasury, stock, credit) BEFORE an agent buys it. POST {target:{payto_address:<token contract>, network:eip155:1|eip155:8453}} returns 0-100 risk, allow/review/block, is_permissioned_security and signals: proxy-aware transfer-restriction scan (ERC-1404/3643/allowlist/pause) with a behavioral transfer simulation, live pause state, issuer identity and issuer OFAC screening. Not investment advice.

Assess an x402 counterparty before paying. POST {target:{payto_address}, payment_context?, policy?}; payto may be a 0x EVM (Base) or base58 Solana seller. Returns risk_score 0-100, decision allow/review/block, confidence, coverage, per-dimension signals, key_factors (what drove the score) and a ready-to-apply recommended_policy. Scored from on-chain settlement behaviour, OFAC sanctions = hard block.

Pre-pay COMPLIANCE screen for regulated onchain flows. POST {target:{payto_address, agent_id?}, payment_context?:{amount,asset}} returns compliance_decision pass/flag/block, diligence_tier, obligations and checks: OFAC sanctions (hard block), counterparty due-diligence tier, structuring detection (sub-threshold payments aggregating within 24h, needs agent_id), FATF Travel-Rule threshold as informational. Screening support, not legal advice.

Buyer-side payment firewall: should THIS agent make THIS payment now? Where /api/assess vets the seller, this vets the payment against your own agent's behaviour. POST {agent_id, payment:{payto_address,amount,resource_url}, context?:{untrusted_text,intended}, policy?} returns allow/hold/block plus 9 signals incl. routing_anomaly, velocity, amount_anomaly, injection_destination, intent_mismatch. Stateful per agent_id.

Same input as /api/assess, but returns a trimmed action-oriented view: the allow/limit/deny decision plus a wallet-ready spending policy (max_payment_usdc per-counterparty cap, daily_cap_usdc, add_to_denylist, require_human_approval) an agent can apply directly to its wallet limits.

Can my x402 service prove it is trustworthy to buyers? 402Sentinel Verified (opt-in trust badge for sellers): deep-audit a service and, if it passes, issue a signed time-boxed 'verified-organic' credential + list it publicly at /api/verified. POST {payto, resource_url?, claimed_buyers?}. Positive-only - failing audits are returned privately, never published.