Solution for fintechs and credit bureaus
Judicial risk is your bureau's blind spot — we close that gap
Integrate real-time lawsuit data into your approval engine. Vigilant surfaces what Serasa, Boa Vista, and SPC don't: active disputes, labor liabilities, tax enforcements, and habitual litigant signals.
Why traditional score isn't enough
Bureaus miss active cases
Labor claims, tax enforcements, and active disputes don't hit the score until they become a formal record — and by then, the loss already happened.
Habitual litigants slip through
A CPF filing 200 claims per year against retailers shows a clean score, but disputes are guaranteed. The pattern only appears in aggregated court history.
Dispute handling eats legal time
Each post-approval dispute costs R$ 200-800 in fees, in-house counsel time, and ops overhead. Preventing 50/month pays for the whole integration.
How it fits into your pipeline
Webhook on onboarding
When a credit application comes in, your backend calls the Vigilant API with the applicant's CPF/CNPJ.
Structured response in seconds
JSON with active cases, labor history, tax enforcements, and litigation signals. Ready for your decision engine to consume.
Score adjusted in real time
Your engine uses the signals as additional features. Approval still runs in milliseconds, zero friction to the end user.
The numbers that matter for your risk
<2s
Average latency
Cache hit on 90% of queries
12
Court sources
Federal + 10 states covering ~70% of volume
R$ 0.10
Per court query
Vs R$ 200-800 per dispute avoided
99.5%
Contractual uptime
Enterprise SLA available
Integrate real-time lawsuit data into your approval engine. Vigilant surfaces what Serasa, Boa Vista, and SPC don't: active disputes, labor liabilities, tax enforcements, and habitual litigant signals.
Blind approval vs informed approval
- Serasa/Boa Vista score as the only judicial signal
- Active dispute invisible until a formal record exists
- Habitual litigant approved without a flag
- Tax enforcement on the CNPJ only shows up in manual due diligence
- Disputes become a recurring cost
- Active cases cross-checked in real time
- Litigation pattern flagged during approval
- CNPJ tax enforcement flagged before disbursement
- LGPD-compliant audit trail ready for compliance
- Predictable disputes become preventive denials
Slots into your decision engines
REST API standardized on OpenAPI 3.1. Running it alongside Serasa / Boa Vista / SPC is just one extra HTTP call in your decision pipeline.
If you already consume bureaus via API, integrating Vigilant takes a few hours. Full documentation and examples at vigilant.trackjud.com.br/api/docs.
How much risk you prevent with Vigilant
Conservative estimate assuming 2% of disputes are prevented from the total analysis volume.
Loss prevented
—
Vigilant cost
—
Net monthly savings
—
Yearly savings
—
Frequently asked questions
Cache-hit responds in <200ms. Cache-miss (data older than 2 days) returns stale data immediately and schedules an async refresh — your onboarding is never blocked. 90% of queries hit cache on average.
Legitimate interest (art. 7 IX of LGPD), since we process public court data for fraud prevention and credit analysis. We keep consent records plus a per-request audit trail.
We don't replace the bureau — we complement it. You keep calling your current engine and add a parallel call to Vigilant. The judicial signals come in as additional features in your score.
R$ 0.10 per court consulted. A typical 3-court analysis costs R$ 0.30. At 5,000 analyses/month across 3 courts = R$ 1,500/month. No minimum fees, credits never expire.
Enterprise contracts have dedicated rate limits, 99.5% SLA with compensatory credit, and regional endpoint. Talk to sales for sizing.
Integrate Vigilant into onboarding today?
Free sandbox with 5 credits. OpenAPI 3.1 docs ready. Test with 10 CPFs and see the payload before talking to sales.