Sanaf AI
Start free
Developer Tools

Cloudsmith, 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 Cloudsmith 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.

  • Developer Tools
  • Connects with a key
  • 10 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 Cloudsmith is

Cloudsmith is a cloud-native artifact management platform for securely managing, distributing, and governing software packages across teams and repositories.

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

How a run works

One message in, the work done in Cloudsmith.

  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 Cloudsmith. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Cloudsmith 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.

10 tools it already has

What it can do in Cloudsmith

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

  • Get Current UserReturn the identity authenticated by the connected Cloudsmith API key. Fails if Cloudsmith reports authenticated=false, even when the HTTP response is 200.
  • Get PackageGet metadata, status, checksums, licensing, and security state for one package in a Cloudsmith repository.
  • Get QuotaReturn current storage and bandwidth usage and allowances for a Cloudsmith namespace without inferring a billing plan name.
  • Get Rate LimitsReturn Cloudsmith's current per-resource request limits, remaining counts, intervals, and throttling state for the authenticated principal.
  • Get RepositoryGet configuration, visibility, usage, and capability details for one Cloudsmith repository without returning repository signing keys or certificates.
  • List OrganizationsList Cloudsmith organizations associated with the authenticated principal so an agent can discover namespace slugs for later calls.
  • List Repository VulnerabilitiesList vulnerability scan summaries for packages in a Cloudsmith repository.
  • Search Audit LogSearch paginated audit events for a Cloudsmith namespace by event, actor, or timestamp text.
  • Search PackagesSearch packages in a Cloudsmith repository by name, filename, version, distribution, architecture, format, or status.
  • Search RepositoriesSearch and list repositories within a Cloudsmith namespace, returning identifiers and summary state without repository signing keys.
Access, and who is in charge of it

You stay the boss of your Cloudsmith 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 Cloudsmith 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 Cloudsmith 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 Cloudsmith 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.

See every app

Questions people ask about Cloudsmith

Can an AI employee really work inside Cloudsmith?
Yes. It signs in to your own Cloudsmith 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 Cloudsmith?
No. Nothing moves and nothing is replaced. Your records stay in Cloudsmith, 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 Cloudsmith account?
You paste in a key from your own Cloudsmith account. It is kept encrypted, and you can withdraw it from inside Cloudsmith 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 Cloudsmith?
It has 10 ready-made tools in Cloudsmith today, among them Get Current User, Get Package and Get Quota. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Cloudsmith 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 Cloudsmith 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 Cloudsmith?
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 Cloudsmith is written down with what it did and when.