Identitycheck
for LuumenAI
Read verification sessions and configs, change them as approved steps
Connect IdentityCheck and your team can ask about verification work in plain language. Look up onboarding sessions and their current status, pull document content, review verification configurations and webhook endpoints. When a configuration needs to change, the agent shows the exact edit first and waits for your approval. Luumen authenticates with an API key.
The Identitycheck toolbox
11 tools: 8 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck API HealthPerforms an API health check to verify endpoint availability and responsiveness.
- ReadFetch All ConfigurationsFetch all existing configurations.
- ReadFetch all notification endpointsFetches all configured notification endpoints (webhooks) for the IdentityCheck SDK.
- ReadFetch ConfigurationFetch a specific identity verification configuration by its code.
- ReadFetch Notification EndpointFetch a notification endpoint by its code.
- ReadFetch OnboardingsRetrieves identity verification onboarding sessions with comprehensive filtering and pagination.
- ReadGet Document ContentRetrieve base64-encoded document content.
- ReadRetrieve Onboarding StatusRetrieve the current status and results of an identity verification onboarding session.
- WriteDelete configurationDelete an existing configuration. Approval by default
- WriteDelete Notification EndpointDelete a notification endpoint by its unique code. Approval by default
- WriteUpdate ConfigurationUpdate an existing configuration. Approval by default
One prompt, start to finish
What a governed Identitycheck 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 — delete configuration, delete notification endpoint, update configuration — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. 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 Identitycheck — 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 Identitycheck to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.