Didit
for LuumenAI
Check verification status in Didit and open new KYC or KYB sessions
Connect Didit and ask about onboarding state in plain language. Look up a user or business profile, read the full decision and feature reports for a session, check which workflow versions are published and what each run costs, and confirm the prepaid credit balance before billable work. When someone needs to re-verify, Luumen creates the hosted session and hands back the URL. Authentication is by API key.
The Didit toolbox
10 tools: 9 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Billing BalanceRead the organization's prepaid Didit credit balance and auto-refill settings before starting billable verification work.
- ReadGet BusinessFetch one aggregated KYB business profile by its exact vendor_data identifier.
- ReadGet UserFetch one aggregated KYC user profile by its exact vendor_data identifier.
- ReadGet Verification DecisionRetrieve the complete current KYC or KYB decision and all feature reports for one verification session.
- ReadGet WorkflowFetch the full configuration and pricing of one workflow version.
- ReadList BusinessesList business profiles aggregated from KYB sessions, including status, session counts, registry identifiers, and verification summaries.
- ReadList UsersList user profiles aggregated from KYC sessions, including status, session counts, and feature summaries.
- ReadList Verification SessionsList and filter KYC, KYB, or standalone verification sessions.
- ReadList WorkflowsList configured verification workflow versions, their publication status, feature summary, and expected per-run pricing.
- WriteCreate Verification SessionCreate a hosted KYC or KYB verification session from a published workflow and return the URL to give the end user. Approval by default
One prompt, start to finish
What a governed Didit run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create verification session — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Didit — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
OktaAccess and posture from Okta, with approval on every change.
Microsoft Entra IDAccess and posture from Microsoft Entra ID, with approval on every change.
Auth0Access and posture from Auth0, with approval on every change.Ping IdentityAccess and posture from Ping Identity, with approval on every change.Put Didit to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.