Sanaf AI
Start free
Video & Audio

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

  • Video & Audio
  • Connects with a key
  • 11 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 VideoDB is

VideoDB is a video infrastructure platform for storing, searching, understanding, editing, and generating video, audio, and image content.

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

How a run works

One message in, the work done in VideoDB.

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

  3. 03

    It does the work

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

11 tools it already has

What it can do in VideoDB

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

  • Ask CollectionQueue a grounded question-answer request over a VideoDB collection's Search V2 indexes. This search-family call is metered and requires Search V2 indexes. The returned status only
  • Create CollectionCreate a VideoDB collection for organizing and searching media. Collections are private by default.
  • Get Async ResultCheck one VideoDB async operation by response ID. Returns its current state or terminal provider result without polling repeatedly, and fails when a completed nested provider respo
  • Get CollectionGet metadata for one VideoDB collection by ID.
  • Get MediaGet metadata for one VideoDB video, audio file, or image.
  • Ingest MediaQueue ingestion of a video, audio file, or image from an HTTP(S) URL into a VideoDB collection. This non-idempotent call is metered; live billing reported fileupload at 0.09 credit
  • List CollectionsList collections available to the connected VideoDB API key and identify the default collection.
  • List MediaList videos, audio files, or images in one VideoDB collection using one normalized media interface. Video results return at most one page and may include an opaque continuation cur
  • Rename MediaRename one VideoDB video, audio file, or image.
  • Search CollectionRun synchronous semantic search over indexed media in a VideoDB collection. This metered call consumed 0.0015 credits per successful call during live Freev1 probing, including call
  • Update CollectionUpdate the name, description, or visibility of an existing VideoDB collection.
Access, and who is in charge of it

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

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