01
Start with one identifier
A business owner enters one of five visible Demo References from this prototype.
Built for Build What Moves IndiaOne GSTIN.
प GST + court record check
One GSTIN.
The whole record.
Before you send goods on credit, check a counterparty reference. This public demo shows how GST and published court-record evidence can become readable, using fictional local fixtures only.
✦ Synthetic report only • Five fictional scenarios • Instant local result
Built for Build What Moves India. This hackathon demo uses synthetic data only. It does not access live government systems, private records, real GSTINs, PANs, Aadhaar numbers, OTPs, payments, or production Parakh data.
DEMO REFERENCE DEMO-2026-0002 · synthetic only
SPECIMENIDENTITYFixture profile found and normalizedCLEAR
FILINGRepeated filing delay pattern in fictional periodsFLAG
2 of 5 on time synthetic periods only
RECORDSFictional public-record example with attributionNOTE
LIMITSNo live records, private ledgers, or payment dataNOTE
Could not find: anything outside these local fictional fixtures.
The citizen journey
Know who you are dealing with.
A small business owner needs to check a supplier, buyer, or logistics partner before extending credit. This prototype makes that one task understandable from start to finish.
02
Make records readable
Parakh normalizes the local business, filing, and public-record fixtures into one evidence trail.
03
Read what is known
The report separates FLAG, CLEAR, and NOTE observations from limits and unavailable evidence.
Live synthetic journey
Try the report yourself.
Choose one of five fictional business situations, or type its listed demo reference. Each opens a dedicated report page using local fixtures only.
The demo accepts only listed demo references. Real-looking personal or government identifiers are blocked.
Why this is clearer
Less hunting. More context.
Today, a counterparty check can mean portal searches, screenshots, filing tables, name variants, and uncertain public-record clues. Parakh puts the available evidence beside the language needed to interpret it responsibly.
THE MANUAL WAY
- Different portals and screenshots
- Periods that are hard to compare
- Name variations without context
- Missing evidence left unexplained
THE PARAKH VIEW
- Normalized period-by-period evidence
- Source and provenance labels
- Confidence with attribution
- Clear limits and what was not found
What works in this prototype
A complete journey, safely shown.
Judges can go from one synthetic identifier to a readable report, compare situations, and download a fixture-only A4 PDF without a login or a live source connection.
01
Local synthetic profile lookup
02
Normalized filing-pattern evidence
03
Synthetic public-record examples
04
Explainable FLAG, CLEAR, and NOTE observations
05
Dedicated report URLs and scenario switching
06
Fixture-only A4 PDF download
Mocked, by design
Honest about what is missing.
This hackathon demo uses synthetic data only. It does not access live government systems, private records, real GSTINs, PANs, Aadhaar numbers, OTPs, payments, or production Parakh data.
Business facts, filing rows, public-record examples, report IDs, confidence language, and provenance labels are all mocked local fixtures. The demo is designed to make that boundary easy to see.
At scale, production use would require authorized APIs, consent-aware handling, audit logs, rate limits, data provenance, retention limits, security controls, and human-readable limitations.
Live production preview
Continue to the live Parakh product.
This public build uses fictional fixtures only. Production Parakh is separate and requires sign-in for authorized real-data workflows.