TRON-native AML/KYT

AML/KYT compliance for TRON, built TRON-first.

Actively-flagged TRON addresses. HMAC-signed webhooks. Append-only audit trail with a public verifier. API access by request: a person issues the key, not a form.

Powered by Nemesis — our TRON-native forensic engine.

No credit card · Sandbox — 10 free calls a month · keys issued on request

—
Flagged TRON addresses
5
official lists with crypto addresses
63
OSINT sources monitored daily
100%
Audit log verifiable
Pricing built for compliance budgets, not procurement theatre

Monthly contracts. No annual lock-in. No "starting from" — the price you see is the price you pay.

Sandbox

Free
10 calls / mo
≈ 3 per week · burst 5/min
  • Full /v1/screen response
  • Public audit verifier
  • HMAC webhooks
  • SLA
  • Email support
Request access →

Developer

$149/mo
2,000 calls / mo
Burst: 30/min · 500/hr
  • Everything in sandbox
  • Idempotency-Key support
  • Email support (24h)
  • Best-effort availability
  • Dedicated channel
Buy in your account →
Most popular

Business

$499/mo
8,000 calls / mo
Burst: 60/min · 2000/hr
  • Everything in developer
  • 16% lower price per check
  • Twice the rate limits
  • Priority email support
Buy in your account →

Growth

$1,500/mo
30,000 calls / mo
Burst: 200/min · 5000/hr
  • Everything in business
  • Uptime SLA (negotiated in MSA)
  • Telegram channel support
  • Quarterly TRON coverage report
  • SOC 2 vendor questionnaire
Buy in your account →

Enterprise

$25k/mo+
Unlimited
Burst: negotiated
  • Everything in growth
  • Private deploy option
  • DPA + custom MSA
  • Dedicated Slack channel
  • Quarterly business review
Request RFP
Cost calculator

Move the slider — see what you pay an enterprise incumbent on TRON vs. GuardPay. Incumbent pricing is the realistic industry mid-market average ($50k/yr base + $0.08 per-call overage), anchored to public marketplace data.

200,000 calls / mo
65% TRON

GuardPay only screens TRON today, so we count TRON volume; non-TRON keeps using your incumbent.

Enterprise incumbent (annual)$147,000
GuardPay (annual)$18,000
You save / year$129,000

Replace, augment, or A/B — we ship monthly contracts and a tamper-evident audit chain so swapping back costs you nothing.

GuardPay vs. the incumbents — on TRON

We don't pretend to match enterprise vendors on BTC/ETH entity attribution. But on TRON-depth coverage — we beat the industry leaders.

GuardPay Enterprise Vendor A Enterprise Vendor B
TRON-specific flagged-address depth—~3,500 est.~2,800 est.
OSINT sources monitored daily63+——
Official lists with crypto addresses: OFAC, UK, Israel, Japan, FBIAll 5YesYes
Behavioural metrics on TRC-2013+ patterns8 patterns7 patterns
3-hop fund-flow graph in every report (SVG export)YesPDF onlyUI only
HMAC-signed webhooksYesYesYes
Idempotency-Key (Stripe-style)YesNoNo
Public audit-chain verifier (no API key)YesNoNo
Monthly contractYesAnnualAnnual
BTC / ETH / SOL entity attribution depthRoadmap, no date yetBest in classBest in class
Forensic Audit — bespoke analysis of complex wallets

When automation hits its limits (mixers, peel-chains, cross-chain, 1,000+ addresses in graph) — our analyst builds the full breakdown by hand. Complete report with outflow tables, fund-flow map, and expert opinion. ~25-30% cheaper than industry-incumbent investigations at comparable TRON-depth quality.

Basic

$4,000– $7,000 / case
24-48 hours · PDF report
  • Up to 50 hops
  • 1-2 exchanges in chain
  • Fund-flow map + outflow table
  • Analyst opinion
Order audit
Most common

Standard

$15,000– $25,000 / case
3-5 business days · PDF + Excel
  • 100+ hops
  • Mixers in chain (Tornado-class)
  • Multiple exchanges + cross-chain
  • Laundering-scheme breakdown
  • Detailed gap analysis
Order audit

Complex

$30k– $65k / case
2-4 weeks · full package
  • 1,000+ addresses
  • Ransomware-class / advanced laundering
  • Peel-chain reconstruction
  • Cross-chain across 3+ networks
  • Court-ready upgrade (+50-100%)
Request quote

Industry-incumbent average for the same case profile is $20-25k. We deliver the same case for $15-18k, with TRON-native depth they lack.

Try the visual graph for free →
API access — by request

We issue keys through a person, not a form: tell us the task and the volume of checks you need, and we reply with the terms, the specification and a key. Existing keys keep working unchanged.

Request access

FAQ for compliance teams

Are you SOC 2?

Our controls follow the SOC 2 framework: data encrypted at rest and in transit, an append-only audit log with a recomputable hash chain, and every code change reviewed before release. The formal Type I audit is on our roadmap. Today we complete your vendor security questionnaire within 48 hours and sign a DPA on request.

Where does your TRON intel come from?

Multiple-jurisdiction sanctions lists, on-chain freeze events (Tether, Circle), 30+ monitored OSINT channels, plus behavioural metrics from the address's TRC-20 history. Specific source identifiers are our moat — never published.

How tamper-evident is the audit log?

Every screen decision writes a content-hashed row to an append-only Postgres log under no-update, no-delete RLS. Rows form a sha256 hash chain rooted in the first entry. Any third party can recompute the chain at /api/audit-verify?recompute=1 without an API key — a hash mismatch proves tampering. On request (Growth+ tier) we anchor periodic chain hashes on-chain for a stronger time-fix; the anchor mechanism is opt-in per customer.

Do you cover EVM / BTC?

In the API (/v1/screen) — TRON only for now. On the website, the free /check already screens EVM addresses (with behaviour analysis) and Bitcoin; bringing them to the API is on the roadmap, no date yet. If >60% of your USDT volume is TRC-20, we are an immediate standalone choice.

How do you handle GDPR / data residency?

The API processes addresses, not personal identifiers (GDPR data-minimisation). Accounts, webhook secrets, and usage logs live in managed Postgres at a tier-1 provider with SOC 2 and at-rest encryption. Separately from the API: this website runs visit analytics and session recording — both off by default and enabled only with explicit consent, with the data described in the Privacy Policy. Specific infrastructure and data residency are confirmed in the DPA on the Growth+ tier.

Can we A/B against our existing vendor?

Yes — explicitly designed for it. Run our /v1/screen in parallel with your current vendor for 90 days. We'll write the gap analysis with you. If we don't catch what they miss on TRON, you walk; no contract.

Stop paying enterprise pricing for TRON coverage that incumbents bolt on as an afterthought.

API access by request. Pilot with us for 90 days at zero cost.

Request access →