# Pinecone

Pinecone vector DB: indexes, collections, upsert, query, fetch, delete. Exposes **21 actions** covering the API surface an agent needs - read and write.

## What it can do

| Method | What it does |
| --- | --- |
| `pinecone_indexes_list` | List all indexes in project - GET /indexes. |
| `pinecone_index_describe` | Describe an index - GET /indexes/{index_name}. |
| `pinecone_index_create` | Create a new index - POST /indexes. |
| `pinecone_index_delete` | Delete an index - DELETE /indexes/{index_name}. |
| `pinecone_index_configure` | Configure an index - PATCH /indexes/{index_name}. |
| `pinecone_index_scale` | Scale an index (pod-based only) - POST /indexes/{index_name}/scale. |
| `pinecone_index_update_metadata` | Update index metadata tags - PATCH /indexes/{index_name}/metadata. |
| `pinecone_collections_list` | List all collections - GET /collections. |
| `pinecone_collection_describe` | Describe a collection - GET /collections/{collection_name}. |
| `pinecone_collection_create` | Create a collection - POST /collections. |
| `pinecone_collection_delete` | Delete a collection - DELETE /collections/{collection_name}. |
| `pinecone_upsert` | Upsert vectors into index - POST /{index_name}/vectors/upsert. |
| `pinecone_query` | Query an index - POST /{index_name}/query. |
| `pinecone_fetch` | Fetch vectors by ID - GET /{index_name}/vectors/fetch. |
| `pinecone_update` | Update a vector - POST /{index_name}/vectors/update. |
| `pinecone_delete` | Delete vectors - DELETE /{index_name}/vectors. |
| `pinecone_list` | List vector IDs in index - GET /{index_name}/vectors/list. |
| `pinecone_describe_stats` | Get index statistics - GET /{index_name}/describe_index_stats. |
| `pinecone_namespaces_list` | List namespaces - GET /{index_name}/namespaces. |
| `pinecone_namespace_upsert` | Upsert vectors to a specific namespace - POST /{index_name}/{namespace}/vectors/upsert. |
| `pinecone_namespace_query` | Query a specific namespace - POST /{index_name}/{namespace}/query. |

## How to get credentials

This connector uses an **API key / token**. Create one in the provider
dashboard, then paste it into FlyMyAI:

- **`PINECONE_API_KEY`** - Pinecone Console - API Keys. (https://app.pinecone.io/)

## Fields to fill in FlyMyAI

| FlyMyAI field | Where it comes from |
| --- | --- |
| `PINECONE_API_KEY` | Pinecone Console - API Keys. |

## Troubleshooting

- **`401 Unauthorized` / `403 Forbidden`** - the token is wrong, expired, or missing a required scope; regenerate it.
- **`429 Too Many Requests`** - provider rate limit; retry after a short backoff.
- **Unexpected `4xx` on writes** - double-check required fields; the agent confirms before write actions.

## Links

- [Pinecone API documentation](https://docs.pinecone.io/reference/api)