Rkvst
for LuumenAI
Read asset provenance in Rkvst, and change app registrations with approval
Rkvst holds the chain of custody for your supply chain data. Luumen reads it in place: asset records, event histories, attachments, app registrations, and tenancy details. Ask who registered an integration or what happened to an asset last week, and get the answer from the ledger. Changes to app registrations and member roles are previewed first and go out as approved steps.
The Rkvst toolbox
24 tools: 22 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload Event AttachmentDownload an attachment from a specified Event on an Asset.
- ReadGet App RegistrationRetrieve details for a given App Registration ID.
- ReadGet AssetRetrieve details for a given Asset.
- ReadGet BlobRetrieve details of a Blob by ID.
- ReadGet EventRetrieve details of a specified Event.
- ReadGet IAM SubjectRetrieve IAM subject details.
- ReadGet MemberRetrieve details for a given Member ID.
- ReadGet Public AssetRetrieve details for a public asset.
- ReadGet Public Asset EventRetrieve a specific public asset event.
- ReadGet TenancyRetrieve details for a specific tenancy.
- ReadList App RegistrationsList all App Registrations.
- ReadList Asset EventsList events for a specified asset.
- ReadList AssetsList all Assets with optional pagination and filters.
- ReadList IAM SubjectsList IAM subjects.
- ReadList MembersList all tenant Members.
- ReadList Public Asset EventsList events for a specific public asset.
- ReadList Public AssetsList all Public Assets.
- ReadList TenanciesList all tenancies.
- ReadRetrieve asset attachment metadataRetrieve metadata for an attachment on a specified Asset.
- ReadRetrieve CapsRetrieve resource limit quotas for a specified service.
- ReadRetrieve Event Attachment MetadataRetrieve metadata for an attachment on a specified Event.
- ReadSearch EventsSearch events matching filter criteria with pagination.
- WritePromote MemberPromote a tenant member to OWNER role. Approval by default
- WriteUpdate App RegistrationUpdate an application's display name or custom claims. Approval by default
One prompt, start to finish
What a governed Rkvst 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 — promote member, update app registration — 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 Rkvst — 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 Rkvst to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.