revettr
Counterparty risk scoring for agentic commerce. Scores wallets, domains, IPs, and companies 0-100 before AI agents transact via x402 micropayments on Base
README
<!-- mcp-name: io.github.AlexanderLawson17/revettr-mcp -->
Revettr
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
pip install revettr
Quick Start
from revettr import Revettr
client = Revettr()
# Score a counterparty — send whatever data you have
score = client.score(
domain="uniswap.org",
ip="104.18.28.72",
wallet_address="0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
)
print(f"Score: {score.score}/100 ({score.tier})")
print(f"Confidence: {score.confidence}")
print(f"Flags: {score.flags}")
if score.tier == "critical":
print("DO NOT TRANSACT")
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": 90,
"tier": "low",
"confidence": 0.75,
"signals_checked": 3,
"flags": [],
"signal_scores": {
"domain": {
"score": 80,
"flags": [],
"available": true,
"details": {
"domain_age_days": 2673,
"dns": {"has_mx": true, "has_spf": true, "has_dmarc": true}
}
},
"ip": {
"score": 100,
"flags": [],
"available": true,
"details": {
"country": "US",
"asn_org": "Cloudflare, Inc.",
"is_private": false
}
},
"wallet": {
"score": 100,
"flags": [],
"available": true,
"details": {
"blockchain": {"tx_count": 100, "unique_counterparties": 29},
"onchain": {"nonce": 16, "eth_balance": 0.072}
}
}
},
"metadata": {
"inputs_provided": ["domain", "ip", "wallet_address"],
"latency_ms": 1185,
"version": "0.1.0"
}
}
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)
score = client.score(wallet_address="0xabc...")
Domain + IP (web service check)
score = client.score(domain="some-api.xyz", ip="185.220.101.42")
Full check
score = client.score(
domain="merchant.com",
ip="104.18.28.72",
wallet_address="0xabc...",
company_name="Merchant LLC",
)
With x402 auto-payment
The client handles x402 payment automatically. You need a funded wallet:
from revettr import Revettr
client = Revettr(
wallet_private_key="0xYOUR_PRIVATE_KEY", # Wallet that pays for the API call
)
# Client automatically handles the 402 → payment → retry flow
score = client.score(wallet_address="0xabc...")
Security: Never hardcode private keys. Use environment variables or a secrets manager in production.
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.
from revettr import SafeX402Client, PaymentBlocked
async with SafeX402Client(
wallet_private_key="0x...",
min_score=60, # Block "high" and "critical" risk
on_fail="block", # Raise PaymentBlocked (default)
) as http:
try:
# Automatically scores the counterparty before paying
response = await http.post("https://some-api.com/endpoint", json=data)
except PaymentBlocked as e:
print(f"Blocked: {e.url} scored {e.score}/100")
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 |
|---|---|---|
| Standard | $0.01 USDC | All available signals based on inputs provided |
Payment is via x402 protocol — USDC on Base network. No API keys, no accounts, no contracts.
API Reference
POST /v1/score
Payment: x402 — $0.01 USDC on Base per request
Request body (JSON):
| Field | Type | Required | Description |
|---|---|---|---|
domain |
string | No | Domain or URL |
ip |
string | No | IPv4 address |
wallet_address |
string | No | EVM address (0x...) |
chain |
string | No | Blockchain network (default: base) |
company_name |
string | No | Name to screen against sanctions |
email |
string | No | Email (future — not scored yet) |
amount |
float | No | Transaction amount in USD (context only) |
At least one of domain, ip, wallet_address, or company_name is required.
GET /health
Payment: None (always free)
Returns API status and signal source availability.
Direct HTTP (without SDK)
# Without payment (returns 402):
curl -X POST https://revettr.com/v1/score \
-H "Content-Type: application/json" \
-d '{"domain": "example.com"}'
# Returns HTTP 402 with payment-required header containing x402 payment terms
Disclaimer
Revettr is an informational tool. It aggregates publicly available signals and returns a risk score. It is not a compliance certification, legal advice, or guarantee of counterparty legitimacy. You are responsible for your own transaction decisions.
Built by
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。