Security & Identity Tools

Rkvst, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Rkvst account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Security & Identity Tools
  • Connects with a key
  • 26 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Rkvst is

DataTrails provides an evidence management platform that delivers a reliable chain of custody for supply chain data, ensuring data authenticity and transparency.

You paste in a key from your own Rkvst account. It is kept encrypted, and you can withdraw it from inside Rkvst whenever you like.

How a run works

One message in, the work done in Rkvst.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Rkvst. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Rkvst account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

26 tools it already has

What it can do in Rkvst

These are the ready-made tools your AI employee already has in Rkvst. It is not limited to them, but it never has to be taught these.

  • Download Event AttachmentTool to download an attachment from a specified event on an asset. use when you have asset uuid, event uuid, and attachment uuid, and want the raw binary content.
  • Get App RegistrationTool to retrieve details for a given app registration id. use after obtaining the application's uuid to inspect its configuration and credentials.
  • Get AssetTool to retrieve details for a given asset. use after you have its uuid; set at time to get historical state.
  • Get BlobTool to retrieve details of a blob by id. use after confirming the blob id.
  • Get EventTool to retrieve details of a specified event. use when you need full metadata, attributes, and associated trails of an existing event in datatrails.
  • Get IAM SubjectTool to retrieve iam subject details. use when you need to fetch details for a specific iam subject by its id.
  • Get MemberTool to retrieve details for a given member id. use after obtaining a valid member uuid.
  • Get Public AssetTool to retrieve details for a public asset. use when you have a public asset uuid.
  • Get Public Asset EventTool to retrieve a specific public asset event. use when you have public asset and event uuids.
  • Get TenancyTool to retrieve details for a specific tenancy. use after you have a tenancy id.
  • List App RegistrationsTool to list all app registrations. use after acquiring a valid auth token to retrieve the applications registered under the tenant.
  • List Asset EventsTool to list events for a specified asset. use after confirming you have the asset uuid.
  • List AssetsTool to list all assets with optional pagination and filters. use when you need to retrieve asset metadata in batches via page size and next page token.
  • List IAM SubjectsTool to list iam subjects. use when you need to retrieve provider-managed subjects, optionally filtering by display name. use after authenticating the tenant.
  • List MembersTool to list all tenant members. use when you need an overview of all users in your tenant.
  • List Public Asset EventsTool to list events for a specific public asset. use when you need to retrieve the event history of a public asset after confirming its public availability.
  • List Public AssetsTool to list all public assets. use when you need to retrieve all assets made public.
  • List TenanciesTool to list all tenancies. use after authenticating to retrieve the tenancy records available to the current tenant.
  • Promote MemberTool to promote a tenant member to owner role. use when you need to elevate permissions after verifying the member identity.
  • Retrieve asset attachment metadataTool to retrieve metadata for an attachment on a specified asset. use after obtaining asset and attachment uuids.
  • Retrieve CapsTool to retrieve resource limit quotas for a specified service. use when checking quota availability before provisioning resources.
  • Retrieve Event Attachment MetadataTool to retrieve metadata for an attachment on a specified event. use when you have asset uuid, event uuid, and attachment uuid and need details like size, hash, and scan status.
  • Retrieve Public Asset Attachment MetadataTool to retrieve metadata for an attachment on a specified public asset. use when you have the public asset uuid and attachment uuid, before downloading the content.
  • Retrieve Public Event Attachment MetadataTool to retrieve metadata for an attachment on a public asset event. use after you have the public asset uuid, event uuid, and attachment uuid.
  • Search EventsTool to search events matching filter criteria with pagination. use when retrieving events by odata filter and paging through large result sets.
  • Update App RegistrationTool to update an application's display name or custom claims. use after retrieving an app registration to apply partial updates to its configuration.
Access, and who is in charge of it

You stay the boss of your Rkvst account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Rkvst account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Rkvst is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Rkvst and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Rkvst

Can an AI employee really work inside Rkvst?
Yes. It signs in to your own Rkvst account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Rkvst?
No. Nothing moves and nothing is replaced. Your records stay in Rkvst, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Rkvst account?
You paste in a key from your own Rkvst account. It is kept encrypted, and you can withdraw it from inside Rkvst whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Rkvst?
It has 26 ready-made tools in Rkvst today, among them Download Event Attachment, Get App Registration and Get Asset. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Rkvst and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Rkvst and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Rkvst?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Rkvst is written down with what it did and when.