AlexanderLawson17/revettr-python

Counterparty risk scoring for agentic commerce. One API call answers: **"Should this agent send money to this counterparty?"**
Revettr scores counterparties by analyzing domain intelligence, IP reputation, on-chain wallet history, and sanctions lists. It's designed for AI agents transacting via x402 on Base.
Install
Quick Start
What Gets Scored
Send any combination of inputs. More data = higher confidence.
| Input | Signal Group | What It Checks |
|-------|-------------|----------------|
| domain | Domain Intelligence | WHOIS age, DNS config (MX, SPF, DMARC), SSL certificate |
| ip | IP Intelligence | Geolocation, VPN/proxy/Tor detection, datacenter vs residential |
| wallet_address | Wallet Analysis | Transaction count, wallet age, counterparty diversity, on-chain behavior |
| company_name | Sanctions Screening | OFAC SDN, EU consolidated, UN consolidated sanctions lists |
Response
Score Tiers
| Score | Tier | Meaning |
|-------|------|---------|
| 80-100 | low | Counterparty appears legitimate |
| 60-79 | medium | Some signals warrant caution |
| 30-59 | high | Multiple risk indicators present |
| 0-29 | critical | Strong risk signals — do not transact |
A score of **0** means a hard match (e.g., exact sanctions hit). This overrides all other signals.
Risk Flags
Flags tell you exactly what triggered a score reduction. They are grouped by signal category:
| Category | Examples | What It Covers |
|----------|----------|----------------|
| Domain | domain_age_under_*, no_mx_records, ssl_* | Domain age, DNS hygiene, SSL validity |
| IP | tor_exit_node, known_vpn, high_risk_country_* | Anonymization, geolocation risk |
| Wallet | wallet_never_transacted, wallet_age_under_* | On-chain history, activity patterns |
| Sanctions | sanctions_exact_match, sanctions_high_confidence_match | OFAC/EU/UN sanctions screening |
The full set of flags and their descriptions are returned in the API response. Flag names are stable and machine-readable.
Usage Examples
Wallet only (minimal)
Domain + IP (web service check)
Full check
With x402 auto-payment
The client handles x402 payment automatically. You need a funded wallet:
> **Security**: Never hardcode private keys. Use environment variables or a secrets manager in production.
With Virtuals Protocol (ACP)
Score seller agents before creating jobs on the Agent Commerce Protocol:
See examples/virtuals_acp_safe_buyer.py for the full buyer agent flow.
Safe Agent Payments
Drop-in replacement for x402 payments that automatically checks counterparty risk before sending money. If the counterparty scores below your threshold, the payment is blocked.
| on_fail | Behavior |
|-----------|----------|
| "block" (default) | Raise PaymentBlocked exception |
| "warn" | Log warning, proceed with payment |
| "log" | Silently log, proceed with payment |
Pricing
| Tier | Price | What You Get |
|------|-------|-------------|