Skip to main content
Integrations · LlamaIndex
Guild agents retrieve ranked text nodes from a LlamaCloud pipeline to answer questions against indexed document collections. Guild stores the API key server-side and injects it at request time, so agent code never sees it. Credential policies let you restrict which agents can call the pipeline and audit every request before it leaves Guild.

Book a demo

See how teams govern agents that use LlamaIndex.

Talk to sales

Get access to Guild, then connect LlamaIndex to your first agent.

What this integration exposes

The integration provides a retrieval tool that runs a query against a managed LlamaCloud pipeline and returns bounded text nodes. The tool uses the llamaindex_ prefix. Use pick() to include only this tool when your agent does not need others from the same set.

How it works

1

Open credentials in Guild

Go to Access & setup > Credentials in Guild. Click Connect and select llamaindex.
2

Paste your API key

Enter your LlamaCloud API key in the API Key field. Guild sends it as a bearer token in the Authorization header on every request.
3

Scope the credential

Choose account, workspace, member, or agent scope. See Credentials for how Guild resolves the right credential at run time.

Why LlamaCloud access needs governing

A LlamaCloud pipeline returns document content to any caller with a valid key. Without controls, any agent in any workspace can query it. Guild’s credential proxy enforces credential policies before each request leaves Guild: ALLOW and DENY rules can restrict the llamaindex_retrieve_from_pipeline operation to specific agents or workspaces, so a pipeline used by one team is not reachable by another. Guild injects the API key server-side after the policy check passes. Agents never receive the key directly, which limits exposure if agent code is compromised. You can tighten scope further by connecting a dedicated credential to a single agent rather than sharing one account-level key across all workspaces.

About the LlamaIndex integration

This integration lets agents query a LlamaCloud pipeline and retrieve ranked text nodes relevant to a given input. Agents can use this to look up information from indexed document collections. Results are bounded and returned directly for use in downstream tasks. The integration is guildai~llamaindex.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect LlamaIndex

In Guild, go to Access & setup > Credentials, click Connect, select llamaindex, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the llamaindex_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~llamaindex:

Frequently asked questions

Yes. Write a credential policy with an agents condition on the llamaindex_retrieve_from_pipeline operation. Guild’s proxy blocks any agent not listed from reaching the pipeline, even if the credential is connected at account scope. See Credential policies.
No. Guild stores the key and adds it as a bearer token in the Authorization header server-side. The agent calls the tool; the proxy injects the credential after the policy check passes.
Yes. Connect one credential at account scope for shared use, then connect a separate credential scoped to a specific workspace. Guild resolves workspace-scoped credentials ahead of account-scoped ones. See Credentials for the full resolution order.
Not yet. The catalog entry for guildai~llamaindex lists no webhook events, so event-driven triggers from LlamaCloud are not available.

Put a governed agent on LlamaCloud this week

Book a demo

See how teams govern agents that use LlamaIndex.

Talk to sales

Get access to Guild, then connect LlamaIndex to your first agent.
Also runs on Guild: Airtable · BigQuery · Hex · Nexla Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026