Live

Read what you’re actually consenting to.

Aonami-labs/lucid

Lucid decodes any Account Aggregator / DEPA consent artefact into plain English — who is asking, what data, why, and how long it is kept. Fully local, no backend, no keys required.

Star on GitHub

Account AggregatorDEPAConsentIndia StackOpen source

Why

Raw AA consent artefacts are opaque JSON or signed JWS that no normal user — and few developers — can read at a glance. So people approve data-sharing they cannot actually see.

How it works

Paste a consent artefact

Drop in raw ConsentDetail JSON (ReBIT PascalCase or camelCase), a full artefact wrapper, or a signed JWS token. Two bundled samples are one click away.

The engine decodes every field

A deterministic, auditable engine maps each field to a plain reading — and always keeps the raw value beside it. It raises notes for indefinite retention, broad scope, and more.

Read it in plain English

Who is asking, what data, why, how it is used, how often, and how long it is kept — as a clear breakdown plus transparency notes. Optionally rephrased even simpler with your own AI key.

Features

Six-part plain-English breakdown

Who · what · why · how used · how often · how long — each with the raw value kept alongside, audit-grade.

Transparency notes that matter

Indefinite retention, stored copies, broad scope, high frequency, expired windows — surfaced as plain-language flags, not a verdict.

Reads every input shape

ReBIT PascalCase and camelCase, full artefact wrappers, and signed JWS — with ISO-8601 or epoch-millisecond timestamps.

Fully local, zero backend

Pure client-side. No server, no secrets, works offline. The full deterministic decode needs no API key.

Bring-your-own-key rephrasing

Optionally rephrase the decode in simpler language — in English or an Indian language — using your own Anthropic, OpenAI, Google, or Groq key.

Decodes, never verifies

If a signature is present, Lucid says so — but never claims it is genuine. A faithful reading of the contents, not proof of authenticity.

Who it's for

For anyone consenting to share financial data on India’s Account Aggregator network — and the developers and policy teams building DEPA tooling.

Open & honest

MIT licensed — open sourceRuns fully local — no data leaves your browserBYOK AI — your key is sent only to your chosen provider, never to AonamiDecodes, doesn’t verify — Lucid never authenticates a signatureNot legal advice

Try it on your consent.

The decoder runs free with no key. Bring your own key for rephrasing.

Star on GitHub

FAQ

No. Lucid decodes and explains the contents of an artefact. If a signature is present it says so, but it holds no keys and does not cryptographically verify anything. Treat a decode as a faithful reading of the contents, not proof of authenticity.

No. The deterministic decode is pure client-side and works offline. The only optional network call is the AI rephrasing layer — and that goes directly from your browser to the provider you chose, using your own key. Nothing is sent to Aonami.

No. The full decode, transparency flags, and raw values all work with zero key. A key is only needed for the optional plain-language rephrasing, and you bring your own — Anthropic, OpenAI, Google, or Groq.

Raw ConsentDetail JSON in ReBIT PascalCase or camelCase, a full artefact wrapper, or a signed JWS token (decoded, never verified). Timestamps can be ISO-8601 strings or epoch milliseconds.

Built under Aonami Labs as an open contribution to India Stack tooling, to showcase DEPA / Account Aggregator consent transparency. Field structures follow the ReBIT AA specification.