Sanaf AI
Start free
Developer Tools

RunPod, 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 RunPod 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
  • 13 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 RunPod is

The Cloud Built for AI - GPU cloud computing platform for AI and machine learning workloads

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

How a run works

One message in, the work done in RunPod.

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

  3. 03

    It does the work

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

13 tools it already has

What it can do in RunPod

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

  • Create RunPod ClusterTool to create a new GPU cluster for multi-node distributed computing workloads on RunPod. Use when you need to deploy multiple pods with shared configuration for parallel processi
  • Create SecretTool to create a new secure secret in RunPod for credential management. Use when you need to store sensitive values like API keys, passwords, or tokens that will be accessible in p
  • Delete Container Registry AuthenticationTool to delete container registry authentication from RunPod. Use when you need to remove stored registry credentials.
  • Delete TemplateTool to remove a RunPod template via GraphQL mutation. Use when you need to delete a template that is no longer needed. The template must not be in use by any pods or assigned to a
  • Get authenticated user infoRetrieve basic information about the authenticated user including ID, email, and security settings. Use this to get the current user's ID, email address, terms of service status, a
  • Get GPU TypesTool to retrieve available GPU types and their specifications, pricing, and availability from RunPod. Use when you need to find GPU options for deployment.
  • Get Pod DetailsRetrieve details of a specific RunPod pod by its unique pod ID. Returns pod configuration including GPU count, memory, cost, and status. Use when you need to check the current stat
  • List CPU TypesTool to retrieve available CPU types and their specifications from RunPod. Use when you need to view CPU options for provisioning pods or selecting hardware configurations.
  • Save Container Registry AuthenticationTool to save container registry authentication credentials for accessing private Docker images in RunPod. Use when you need to store credentials for a private container registry.
  • Save Serverless EndpointTool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings. Use when configuring new GPU-accelerated serverless endpoints or modifying existi
  • Save TemplateTool to create a new RunPod template or update an existing one with container configuration. Use when you need to define reusable pod/serverless configurations with specific images
  • Update Registry AuthTool to update existing container registry authentication credentials in RunPod. Use when you need to modify the username or password for an existing registry authentication.
  • Update User SettingsTool to update current user settings (e.g., SSH public key) in RunPod. Use when you need to configure SSH access to pods by setting the user's SSH public key.
Access, and who is in charge of it

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

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