Artificial Intelligence

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

  • Artificial Intelligence
  • Signs in to your account
  • 30 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 Pinecone is

Long-term Memory for AI. The Pinecone vector database makes it easy to build high-performance vector search applications. Developer-friendly, fully managed, and easily scalable without infrastructure hassles.

You sign in with your own Pinecone account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Pinecone.

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

  3. 03

    It does the work

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

30 tools it already has

What it can do in Pinecone

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

  • Cancel Bulk ImportTool to cancel a bulk import operation in Pinecone. Use when you need to stop an ongoing import operation that is not yet finished.
  • Configure IndexTool to configure an existing Pinecone index, including pod type, replicas, deletion protection, and tags. Use when you need to scale an index vertically or horizontally, enable/di
  • Create BackupTool to create a backup of a Pinecone index for disaster recovery and version control. Use when you need to preserve the current state of an index including vectors, metadata, and
  • Create IndexTool to create a Pinecone index with specified configuration. Use when you need to initialize a new vector database index for storing and querying embeddings.
  • Create Index from BackupTool to create an index from a backup. Use when you need to restore or duplicate index data from a previously saved backup.
  • Create Index with Embedding ModelTool to create a Pinecone index with integrated embedding model for automatic vectorization. Use when you need to set up a new index that automatically converts text to vectors usi
  • Create NamespaceTool to create a namespace within a serverless Pinecone index. Use when you need to organize vectors into isolated partitions.
  • Delete IndexTool to permanently delete a Pinecone index. Use when you need to remove an index from your project. Note: Deletion protection and pending collections can prevent deletion.
  • Delete NamespaceTool to permanently delete a namespace from a serverless index. Use when you need to remove an entire namespace and all its data. This operation is irreversible and only supported
  • Describe BackupTool to retrieve detailed information about a specific backup. Use when you need to check backup status, configuration, or metadata.
  • Describe Bulk ImportTool to describe a specific bulk import operation in Pinecone. Use when you need to retrieve detailed information about an import's status, progress, timing, and any errors.
  • Describe Index StatsTool to get index statistics including vector count per namespace, dimensions, and fullness. Use when you need to understand the contents and status of an index.
  • Describe Restore JobTool to get detailed information about a specific restore job in Pinecone. Use when you need to check the status, progress, or metadata of a restore operation.
  • Generate EmbeddingsTool to generate vector embeddings for input text using Pinecone's hosted embedding models. Use when you need to convert text into vector representations for semantic search or sim
  • Get Model InformationTool to retrieve detailed information about a specific model hosted by Pinecone. Use when you need to understand model capabilities for embedding and reranking operations.
  • List Available ModelsTool to list all available embedding and reranking models hosted by Pinecone. Use when you need to discover available models or filter by model type (embed/rerank) or vector type (
  • List Bulk ImportsTool to list all recent and ongoing bulk import operations in Pinecone. Use when you need to monitor or track the status of data import jobs. Supports pagination with a default lim
  • List CollectionsTool to list all collections in a Pinecone project (pod-based indexes only). Use when you need to view available collections.
  • List Index BackupsTool to list all backups for a specific Pinecone index. Use when you need to view available backups for an index. Supports pagination via limit and paginationToken parameters.
  • List IndexesTool to list all indexes in a Pinecone project. Use when you need to retrieve all indexes with their configurations and status information.
  • List NamespacesTool to list all namespaces in a serverless Pinecone index. Use when you need to discover available namespaces for data organization. Returns up to 100 namespaces by default with p
  • List Project BackupsTool to list all backups for indexes in a Pinecone project. Use when you need to retrieve backup information across all project indexes. Supports pagination with limit and paginati
  • List Restore JobsTool to list all restore jobs for a project with pagination support. Use when you need to view the status of restore operations or track restore progress.
  • List VectorsTool to list vector IDs in a Pinecone serverless index. Use when you need to browse or retrieve vector identifiers from a namespace. Supports filtering by prefix and pagination for
  • Query VectorsTool to perform semantic search within a Pinecone index using a query vector. Retrieves IDs and similarity scores of the most similar items, ordered from most to least similar. Eit
  • Rerank DocumentsTool to rerank documents by semantic relevance to a query. Use when you need to order retrieved documents by their semantic relevance to a user's search query using Pinecone's host
  • Search Records in NamespaceTool to search records within a Pinecone namespace using text, vector, or ID query. Use when you need to find similar records based on embeddings or record IDs. Results can optiona
  • Start Bulk ImportTool to start an asynchronous bulk import of vectors from object storage (S3, GCS, or Azure Blob Storage) into a Pinecone index. Use when you need to import large volumes of vector
  • Update VectorTool to update a vector in Pinecone by ID. Use to overwrite vector values and/or metadata. Supports bulk updates via metadata filters.
  • Upsert Records to NamespaceTool to upsert text records into a Pinecone namespace. Use when you need to add or update records with automatic text-to-vector conversion.
Access, and who is in charge of it

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

Can an AI employee really work inside Pinecone?
Yes. It signs in to your own Pinecone 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 Pinecone?
No. Nothing moves and nothing is replaced. Your records stay in Pinecone, 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 Pinecone account?
You sign in with your own Pinecone account, the same way you already do. We never see or hold your password. 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 Pinecone?
It has 30 ready-made tools in Pinecone today, among them Cancel Bulk Import, Configure Index and Create Backup. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Pinecone 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 Pinecone 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 Pinecone?
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 Pinecone is written down with what it did and when.