Pinecone connector icon

Pinecone Connector

Build in-app semantic search, retrieval augmented generation and vector storage workflows. Cyclr lets SaaS teams embed Pinecone upsert, query and fetch operations as customer-facing integrations without exposing vendor keys.

Build with this Connector Talk to an integration expert
01

Faster time to market

Low-code flows accelerate integration development.

02

Multi-tenant controls

Govern usage per customer and restrict operations.

03

Operational reliability

Built-in retries and rate-limit handling.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Cyclr’s low-code builder connects your app to Pinecone so you can store embeddings, run nearest-neighbor queries and fetch records as part of product workflows. Publish integrations in your embedded marketplace, orchestrate multi-step pipelines, and expose supported methods as governed MCP tools for tenants.

PRODUCT USE CASES

Use cases

Quickly add persistent vector storage and semantic search to your offering. Publish Pinecone integrations in your white-label marketplace and expose governed MCP tools to customers for safe, auditable use.

In-app semantic search for customer data

Store customer embeddings in Pinecone and expose a managed search tool inside your product for fast similarity search.

Retrieval augmented generation pipelines

Orchestrate embeddings, match queries and post-process results to power RAG features in multi-tenant SaaS products.

Enrich analytics with vector metadata

Upsert vectors with metadata and use filterable queries to drive smarter dashboards, recommendations and user segmentation.

ORCHESTRATION

How Pinecone works with Cyclr

Cyclr sits between your SaaS product and Pinecone to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Pinecone

    Pinecone processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Pinecone methods you can orchestrate through Cyclr.

Reranking1

Rerank Documents

Action

Rerank results according to their relevance to a query.

Models2

Get Model

Action

Get a model.

List Models

Action

List all models.

Embeddings1

Generate Vectors

Action

Generate vector embeddings for input data.

Backups10

List Restore Jobs

Action

List all restore jobs.

Create Backup

Action

Create a backup of an index.

List Backups By Index

Action

List all backups by index.

Create Index From Backup

Action

Create an index from a backup.

Get Restore Job

Action

Get a restore job.

List New Restore Jobs

Action

List all restore jobs created since the last successful run.

List Backups

Action

List all backups.

List New Backups

Action

List all backups created since the last successful run.

Get Backup

Action

Get a backup.

Delete Backup

Action

Delete a backup.

Indexes8

Create Pod Based Index

Action

Create a pod based index.

Get Index

Action

Get an index.

Configure Pod Based Index

Action

Configure a serverless index.

Create Serverless Index

Action

Create a serverless index.

Configure Serverless Index

Action

Configure a serverless index.

Create Index With Integrated Embedding

Action

Create an index with integrated embedding.

List Indexes

Action

List all indexes.

Delete Index

Action

Delete an index.

Collections4

Delete Collection

Action

Delete a collection.

Create Collection

Action

Create a collection.

List Collections

Action

List all collections.

Get Collection

Action

Get a collection.

Index14

List Namespaces

Action

List all namespaces.

List Vectors By ID

Action

List vectors by vector ID.

Get Namespace

Action

Get a namespace.

Delete Namespace

Action

Delete a namespace.

Get Index Statistics

Action

Get the statistics of the index.

Search Text By ID

Action

Search with text by ID.

Search Text By Vector

Action

Search with text by vector.

Search Vector

Action

Search with a vector.

Search Text By Inputs

Action

Search with text by inputs.

Delete Vectors

Action

Delete one or more vectors.

Update Vector

Action

Update a vector.

Upsert Vectors

Action

Upsert vectors into a namespace.

Upsert Text

Action

Upsert text into a namespace.

List Vector IDs

Action

List all vectors IDs.

TECHNICAL DETAILS

Pinecone integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Pinecone integrations in Cyclr.

API and authentication

API host
https://api.pinecone.io.
Authentication
API key (header)
Credentials

Api-Key header and the index data-plane host (index-specific URL).

Method categories

Index management, vector operations (upsert/query/fetch/delete), metadata filters, stats and hybrid search.

View vendor API documentation →

Pagination and rate limits

Pagination

Large fetches use paginationToken. fetch_by_metadata returns pagination.next; fetch responses are limited to 10,000 records or 4MB per response.

Rate limits

Per-namespace request-per-second limits apply (e.g., 100 rps for query/upsert/delete/update). Exceeding limits returns 429; use exponential backoff or request higher quotas.

IMPLEMENTATION

Authentication at a glance

Pinecone requires a project API key. Send Api-Key header with JSON requests. Discover index-specific data-plane host via the console or describe_index.

Authentication method
API key (header)
Credential required

Api-Key header and the index data-plane host (index-specific URL).

Before you begin:

Target the index-specific data-plane host; do not use only the generic control-plane URL for data operations.

View setup guide

COMMON QUESTIONS

Frequently asked questions

Provide a Pinecone project API key (sent as the Api-Key HTTP header) and the index-specific data-plane host URL available from the Pinecone console or describe_index.

Yes. Cyclr can encapsulate credentials, expose limited Pinecone methods as governed MCP tools and apply tenant-level controls and auditing.

All Pinecone HTTP requests must include a valid Api-Key header and use JSON content-type. SDKs accept the same project API key for client initialization.

Use paginationToken returned by fetch_by_metadata or the SDK helper methods. Limit requests to avoid the 4MB response cap and 10,000 record page limits.

KEEP EXPLORING

Related resources and connectors

Documentation

How to develop an API – Best Practices to Follow from Cyclr Developers

Read more →Product

MCP PaaS

Read more →Related connector

Amazon S3

Related Data Tools connector for customer-facing integration workflows.

Related connector

DataDog

Related Data Tools connector for customer-facing integration workflows.

Related connector

ElasticSearch

Related Data Tools connector for customer-facing integration workflows.

Let Cyclr handle the integrations.

You focus on building the product your customers love.

Start building for free Get a demo