Integrations · Pinecone
Guild agents query a Pinecone Assistant for ranked text snippets from the files you uploaded to it, so the agent answers from your documents. Guild stores your Pinecone API key and injects it server-side, so agent code never sees it.
Book a demo
See how teams govern agents that use Pinecone.
Talk to sales
Get access to Guild, then connect Pinecone to your first agent.
What the Pinecone integration exposes
The integration isguildai~pinecone-assistant. It has one tool, pinecone_assistant_context_assistant, which calls the Assistant context API: it takes an assistant name and a query and returns the most relevant snippets with their sources. It doesn’t chat, upload files, or query a vector index directly.
Requests go to Pinecone’s Assistant data plane at https://prod-1-data.ke.pinecone.io.
How it works
1
Create a Pinecone API key
In the Pinecone console, open API keys and create a key for the project that holds your assistant.
2
Connect the key in Guild
Go to Access & setup > Credentials, click Connect, select pinecone-assistant, and paste the key into API Key.
3
Import the tool
Import
PineconeAssistantTools from @guildai-services/guildai~pinecone-assistant and add it to the agent’s tools. Tell the agent the assistant’s name in its prompt.Authentication
- Type: API key
- Header: Guild sends the key as
Api-Key: <key>
Usage
Tools
Tools in the latest published version ofguildai~pinecone-assistant:
Frequently asked questions
Can the agent search a Pinecone vector index?
Can the agent search a Pinecone vector index?
No. The tool reads from a Pinecone Assistant only. To query an index, create a custom integration against your index host.
Can the agent add files to the assistant?
Can the agent add files to the assistant?
No. Upload files in the Pinecone console or with Pinecone’s own SDK. The agent only retrieves context.
Can one API key reach several assistants?
Can one API key reach several assistants?
Yes. The key covers every assistant in its Pinecone project, and the agent picks one by name on each call. Use a separate key, and a separate Guild credential, to keep agents to different projects.