Synthetic report

Aarav Cloudpetal Demo Supplies record

This report mirrors the Parakh report journey, but every source and business fact is synthetic.

Demo reference
DEMO-2026-0001
Report ID
PRK-SYN-CLEAR-001

DEMO REFERENCE DEMO-2026-0001 · Uttar Pradesh

Aarav Cloudpetal Demo Supplies Private Limited

SPECIMEN
IDENTITY
Synthetic profile found
CLEAR
FILING
Recent filing pattern is consistent
CLEAR
RECORDS
1 synthetic registry record(s) found
CLEAR
LIMITS
3 unavailable source area(s) disclosed
NOTE

Could not find: Live GST portal confirmation, Authorized bank-account verification, Human review of original public-record documents.

AI identity check

Fictional evidence · runtime AI

Does this record belong to the same business?

A similar name is a reason to check, not a confirmed identity. Compare the source fields with the model’s explanation.

[E1] BUSINESS YOU ARE CHECKING

Aarav Cloudpetal Demo Supplies Private Limited

Trade name: Aarav Cloudpetal Demo Supplies

Synthetic entity marker: DEMO-ENTITY-CLEAR

[R1] NAME ON THE RECORD

Aarav Cloudpetal Demo Supplies Private Limited

DEMO-RECORD-0011 · Fictional registry entry

Synthetic entity marker: DEMO-ENTITY-CLEAR

AI Attribution ReasoningDEMO-RECORD-0011THINKING
Reviewing the synthetic entity and candidate record…
See the exact evidence sent to AI

These fields are fictional. The model is not given the fixture’s expected decision, confidence, or match explanation. Identity markers are invented tokens, not PANs.

{
  "synthetic": true,
  "mode": "full",
  "E1": {
    "source": "Fictional business profile",
    "legalName": "Aarav Cloudpetal Demo Supplies Private Limited",
    "tradeName": "Aarav Cloudpetal Demo Supplies",
    "aliases": [
      "Aarav Cloudpetal Demo Supplies Pvt Ltd",
      "Aarav Cloudpetal Demo"
    ],
    "entityMarker": "DEMO-ENTITY-CLEAR"
  },
  "R1": {
    "source": "Ministry of Corporate Affairs / Registry Ledger (Demo)",
    "reference": "DEMO-RECORD-0011",
    "category": "registry",
    "namedParty": "Aarav Cloudpetal Demo Supplies Private Limited",
    "parties": [
      "Aarav Cloudpetal Demo Supplies Private Limited"
    ],
    "entityMarker": "DEMO-ENTITY-CLEAR"
  }
}

What changes when evidence is missing?

Remove both identity markers and ask AI again using the same names. The result below is a separate live experiment; it does not replace your report.

Your next step: ask the business for a document showing its registered legal name and identifier. Compare it with the original record before linking the two. No documents are uploaded in this demo.

Synthetic-data disclosure: This public synthetic demo uses fictional data only. It does not access live government systems, private records, real GSTINs, PANs, Aadhaar numbers, OTPs, payments, or production Parakh data.
CICRA 2005 note: This synthetic demonstration is not a credit information report, legal opinion, or automated credit decision.

SYNTHETIC DEMO - NOT A REAL REGISTRATION

AI Summary

Thinking

Reviewing the synthetic evidence and record attributions…

The synthetic findings remain available while AI synthesis is pending or unavailable.

Who you are dealing with

Identity and structure

Legal name
Aarav Cloudpetal Demo Supplies Private Limited
Trade name
Aarav Cloudpetal Demo Supplies
Constitution
Private Limited Company
State
Uttar Pradesh
Status
Active in synthetic registry
Synthetic registry since
12 Jan 2026
Address
Plot No. 48/B, Phase 1, Industrial Area Site 4, Sahibabad, Ghaziabad, Uttar Pradesh 201010 (Fictional commercial address)
Source
Local synthetic fixture, generated for Parakh demo

Statutory returns & timing compliance

GST return filing

Returns filed on time

Available filing data covers 5 fixture periods. GSTR-1 and GSTR-3B filings are evaluated against standard statutory due dates.

CLEAR
ReturnPublishedOn timeLateSource unavailable
GSTR-15500
GSTR-3B5500
GSTR-1MAR 26 – JUL 26
MAR26
APR26
MAY26
JUN26
JUL26
GSTR-3BMAR 26 – JUL 26
MAR26
APR26
MAY26
JUN26
JUL26
On timeLateNot available from source
PeriodGSTR-1GSTR-3BFiled on
Mar 2026filedfiled09 Apr 2026
Apr 2026filedfiled10 May 2026
May 2026filedfiled08 Jun 2026
Jun 2026filedfiled10 Jul 2026
Jul 2026filedfiled09 Aug 2026

Court and record examples

Public-record signals

CLEARSYN-REG-CLEAR-011
10 Aug 2026

The synthetic registry fixture reports active operational status, a matching registered office, and an exact legal-name/entity-marker match.

DEMO-RECORD-0011 · Ministry of Corporate Affairs / Registry Ledger (Demo)

Parties: AARAV CLOUDPETAL DEMO SUPPLIES PVT LTD

Side: named-party · Fixture descriptor: Exact synthetic legal-name match

Fixture confidence High · Local synthetic fixture, generated for Parakh demo

AI Attribution ReasoningSYN-REG-CLEAR-011THINKING
Reviewing the synthetic entity and candidate record…

Evidence, not rating

Observations

CLEARSynthetic profile found

The searched identifier resolves to a local synthetic business profile with a legal name, trade name, state, and registration marker.

Confidence High · Synthetic business profile lookup

CLEARRecent filing pattern is consistent

Available synthetic returns show regular filing markers across the recent periods included in this demo.

Confidence High · Derived from synthetic GST filing fixture rows

CLEARName alignment found

The synthetic registry fixture reports active operational status, a matching registered office, and an exact legal-name/entity-marker match.

Confidence High · registry record SYN-REG-CLEAR-011

NOTERead with demo limitations

This demo explains what the evidence says and what it cannot say. It does not score, rate, or clear a counterparty.

Confidence Medium · Report methodology note

How this report was generated

  1. 01Accept only an obvious synthetic identifier
  2. 02Load local synthetic profile, filing, and public-record fixtures
  3. 03Normalize names, dates, filing periods, and record parties
  4. 04Create observations with FLAG, CLEAR, and NOTE labels only
  5. 05Run server-side AI attribution reasoning for each returned public-record signal
  6. 06Render model decision, confidence, justification, or fixture-grade fallback
  7. 07Synthesize the resolved attribution results and filing evidence into one descriptive AI Summary
  8. 08Attach confidence, attribution, provenance, limits, and synthetic disclosure

Production use would require authorized APIs, consent-aware handling, audit logs, rate limits, data provenance, retention limits, security controls, and human-readable limitations.

Back to search