LlamaIndex Framework
by LlamaIndex Agent framework in Agent frameworks & SDKs
Library Agent-ready
LlamaIndex, Inc. · llamaindex.ai · who's behind it
The LlamaIndex Framework is LlamaIndex's open-source Python toolkit for retrieval and agents, with FunctionAgent, ReActAgent and CodeActAgent, multi-agent AgentWorkflow, event-driven Workflows, MCP tools and hundreds of integration packages.
Best for Python teams building retrieval-heavy agents over their own data, with many connectors.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Frameworks. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
More from LlamaIndex LlamaParse API + MCP (Documents)
Assessment. An MIT Python framework for retrieval and agents, with three agent types, multi-agent AgentWorkflow, resumable event-driven Workflows, MCP tools and a huntr bug bounty, and no telemetry found. Core is still 0.14 with breaking minors, OpenAI is the silent default, and approval and injection handling are left to the application.
Facts
Access how an agent reaches and pays for it
- Auth
- None
- Pricing
- Free · Free · OSS
- x402
- No
- Licence
- MIT
Where it lives packages, source, docs and releases
- Packages
pypillama-indexpypillama-index-corepypillama-index-workflowspypillama-index-tools-mcp- llms.txt
- published
- Last release
- GitHub stars
- 53k
- PyPI / week
- 1.3M
From our research 8 facts checked against the vendor's pages
- Surface listed
- The LlamaIndex Framework for Python (llama-index and llama-index-core) with llama-index-workflows, read from the run-llama/llama_index and run-llama/workflows-py repositories, developers.llamaindex.ai (llms.txt, agents and MCP guides) and OSV on 6 November 2026. Nothing was installed
- Scope
- The open-source framework. LlamaParse, LlamaIndex's hosted document parser, and OpenDocRouter have separate Anchor Terminal listings. A TypeScript edition exists and wasn't graded
- Agents
- FunctionAgent for provider tool calling, ReActAgent and CodeActAgent for prompted tool use, and AgentWorkflow for hand-offs between agents
- Workflows
- Event-driven steps with context that can be serialised and resumed, human-in-the-loop events, and a DBOS package for durable runs
- MCP
- llama-index-tools-mcp loads tools from MCP servers, and workflows can be served as MCP servers
- Defaults
- OpenAI for the LLM and embeddings unless Settings is changed; ChatMemoryBuffer for agent memory
- Telemetry
- None found in llama-index-core. Instrumentation and callback handlers export to observability tools when configured
- Versioning
- 0.14.x for core with breaking changes at minor versions such as 0.13 and 0.14; Workflows is at 2.x
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- FunctionAgent, ReActAgent, CodeActAgent and multi-agent AgentWorkflow over one Workflows engine
- Workflow context serialises and resumes, with a DBOS package for durable runs
- Hundreds of integration packages for models, vector stores and data loaders
- No telemetry found in llama-index-core
- huntr bug bounty and public advisories with fixed versions
Weaknesses
- Core is 0.14.x, and minor versions such as 0.13 and 0.14 carried breaking changes
- OpenAI is the default LLM and embedding provider unless Settings is changed
- No per-tool approval primitive; the threat model leaves input validation to the application
- Several 2025 path-traversal and denial-of-service advisories in core and readers
Before you call it notes for agents
- Set Settings.llm and Settings.embed_model explicitly so calls don't go to OpenAI by default
- Install llama-index-tools-mcp for MCP tools and pass only the allowed tools the task needs
- Use Workflow human-in-the-loop events before tools that write or send
- Pin llama-index-core to a minor version, since minors have broken APIs
- Upgrade llama-index-core to 0.13.0 or later to clear the 2025 advisories
Who's behind it provenance 61/100
- Legal entity namedLlamaIndex, Inc.20/20
- Domain agellamaindex.ai, no registry record we could read0/15
- Endpoint on the vendor's domainno hosted endpointn/a
- Terms of servicenothing hosted, so the MIT licence stands in10/10
- Privacy policyread, states 7 of the 8 things a reader expects9.3/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtcould not be fetched0/10
- People named2 named with their role, none with a public profile7/10
- Support routea community5/5
Terms and privacy, as read
Terms of service none to read
TL;DR Nothing is hosted by the vendor, so there are no terms of service to read. The MIT licence stands in and the check scores in full.
Privacy policy dated 2026-08-24, states 7 of 8, 1 to know
TL;DR Dated 2026-08-24. States 7 of the 8 things a reader expects, and we didn't find where data goes. To know before relying on it, selling or sharing data for advertising.
Says it sells personal data or shares it for advertising
We may share a common account identifier (such as a hashed email address or user ID) with our third-party advertising partners to help link the personal data we and our third-party partners collect to the same person, or otherwise target advertising to an individual on a third-party website or platform.
Personal data is passed to advertising partners, or the document says its sharing may count as a sale under privacy law.
Gives the date it was last updated Last updated 2026-08-24
Last Updated: Aug 24, 2026
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
The categories of personal data we collect depend on how you interact with us and our services.
The basic statement a privacy policy exists to make.
Says how long data is kept
We will usually retain the personal data we collect about you for no longer than reasonably necessary to fulfil the purposes for which it was collected, and in accordance with our legitimate business interests and applicable law.
Says when data sent to the service is deleted.
Says who else receives the data
A “processor,” which is sometimes referred to as a “service provider,” processes personal data on behalf of a controller subject to the controller’s instructions.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising
This information is used to provide and inform targeted advertising, as well as to provide advertising-related services such as reporting, attribution, analytics, and market research.
A plain statement either way.
Says what rights people have over their data
We value your privacy and your rights as a data subject and have therefore appointed Prighter Group with its local partners as our privacy representative and your point of contact for the following regions:
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact privacy@runllama.ai
If you have any questions or requests in connection with this Privacy Notice or other privacy-related matters, please send an email to privacy@runllama.ai.
An address or officer to send a request to.
Says where data is transferred or stored
Not found in the text.
The countries data goes to and the safeguard used.
Customer content, including uploaded files and documents, is used to improve the services as well as to run them.
We use this content primarily to provide you with our services, to facilitate your requests, and to improve our services.
Noted by a second reader on 2026-10-08.
Business partners that receive personal data may use it for their own business and commercial purposes.
Our business partners may use your personal data for their own business and commercial purposes, including to send you information about their services.
Noted by a second reader on 2026-10-08.
Disconnecting Google Drive stops further access but does not delete customer content already sent to the services.
Disconnecting Google Drive does not delete Customer Content previously provided to our services.
Noted by a second reader on 2026-10-08.
The document · read 2026-10-08 · 5,430 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The framework is MIT-licensed; the company facts follow the LlamaParse listing.
developers.llamaindex.ai/robots.txt allows all crawlers.
The privacy policy link is the company's; the library collects nothing itself. Neither the terms nor the privacy policy was re-read for this listing.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
LlamaIndex on LinkedIn @llama_index GitHub
Raised $27.5M in total, as of March 2025 source
Backed byGreylock,Norwest,Jack Altman,Lenny Rachitsky,Mathilde Collin,Raquel Urtasun,Joey Gonzalez
Researched 6 November 2026 from public pages. LlamaIndex's seed announcement on its own blog, written by Jerry Liu and read 28 October 2026, says he built GPT Index, later renamed LlamaIndex, and joined forces with Simon Suo two months in to develop it. Its about and careers pages name no one in their served text, and its Series A post names no founder. Greylock's portfolio page (https://greylock.com/portfolio/llamaindex/) lists the leadership as Jerry Liu, CEO & Co-Founder, and Simon Suo, CTO & Co-Founder; as only an investor page gives those titles, the roles stay Co-founder. OpenDocRouter's site says it is made by LlamaIndex and names no person. Copied from the LlamaParse listing (checked 29 October 2026) for the LlamaIndex Framework on 6 November 2026; nothing newer was looked for. On 6 November 2026 a search for a newer round or a valuation found only databases and trackers the rules exclude; neither the seed nor the Series A post states a valuation, so none is given. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 16:01 UTC
- github
run-llama/llama_indexv0.14.25, released 2026-09-21 - pypi
llama-index0.14.25, released 2026-09-21 - pypi
llama-index-core0.14.25, released 2026-09-21 - pypi
llama-index-tools-mcp0.6.0, released 2026-08-31 - pypi
llama-index-workflows2.26.1, released 2026-10-21 - GitHub stars 53k
- PyPI downloads a week 410k
- security.txt none · 1 hour ago
- llms.txt answers · 2 hours ago
Pages we watch
| Page | Kind | Last checked | Last changed |
|---|---|---|---|
| raw.githubusercontent.com/run-llama/llama_index/main/CHANGE… | changelog | 3 hours ago · 200 | no change seen |
| www.llamaindex.ai/privacy-policy | privacy | 3 hours ago · 200 | 27 hours ago |
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/llamaindex.json
Notable
- llama-index-core 0.14.25 is the newest core release, in the changelog entry of 21 September 2026; the previous one was 19 August, while integration packages publish separately source
- Workflows live in run-llama/workflows-py as llama-index-workflows, 2.26.1 on 21 October 2026, beside the llama-agents server and DBOS durability packages source
- SECURITY.md runs a bug bounty on huntr for llama-index, llama-index-core, the OpenAI integrations and llama-index-cli, and its threat model puts input validation on the hosting application source
- OSV lists path-traversal, denial-of-service, temporary-file and pickle-serialiser advisories for llama-index-core first published between July and September 2025, all fixed by 0.13.0, and one more (GHSA-488g-hw5f-x29p) on 2 February 2026, fixed in 0.12.41 source
- Earliest tag in the repository is v0.2.17 of 28 January 2023 source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using LlamaIndex Framework, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used LlamaIndex Framework, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 14.0 | |
| Local-package reading. Official PyPI packages with Python 3.10 to below 4.0 (20). Public unit-test, type-check, lint, coverage and CodeQL workflows, with the type-check, lint and CodeQL runs on main passing on 3 November (25). 379 open issues and 1,291 open issues and pull requests on 6 November, with 241 issues opened in the 90 days to 3 November. Of the 50 newest, 28 had a comment and 3 were closed; a stale bot and an issue classifier run on the repository (12). A dated, generated changelog per package, but core is 0.x and minors such as 0.13 and 0.14 carried breaking changes (8). Core isn't 1.0; Workflows is at 2.x, so partial (5). 20+25+12+8+5 = 70. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 13.8 | |
| Framework reading. A typed Python API with a generated reference (22). llms.txt indexing the framework docs, plus a docs search API and an MCP server for the docs (10). The agents guide says what each agent class is for, and the MCP page lists the three ways to use MCP (15). Tools are typed from function signatures and Pydantic models (13). Many examples and notebooks, few documented error types (10). Dated changelog (15). 22+10+15+13+10+15 = 85. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 11.9 | |
| Framework reading. MCP tools through a separate llama-index-tools-mcp package, with allowed tools selectable (18). Memory token limits, iteration caps and streaming events (16). Tool errors returned to the agent, with few typed errors (12). Workflow context serialises and resumes, and the DBOS package makes runs durable (16). Few required parameters, but OpenAI is the silent default for LLM and embeddings, Python here with a separate TypeScript edition (11). 18+16+12+16+11 = 73. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 12.9 | |
| Framework reading (telemetry defaults, approvals, guardrails, sandboxing). No telemetry found in llama-index-core (25). Human-in-the-loop events in Workflows and agents can wait for a person, but there's no per-tool approval primitive and CodeActAgent's executor is the developer's to supply (12). The threat model puts input validation on the application, with no prompt-injection guidance in the agent pages (5). Instrumentation events and callback handlers for tracing (14). A huntr bug bounty, GitHub private reporting and public advisories with fixed versions (18). 25+12+5+14+18 = 74. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 7.5 | |
| Self-hosted rule. Free MIT packages with nothing to buy for the framework itself (20 + 20 + 20). No payment protocol (0). LlamaCloud is graded on its own listing. 0+20+20+20 = 60. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 6.0 | |
| llama-index-core 0.14.25 on 21 September 2026, 46 days before this check (20). Two core changelog entries in the 90 days (19 August and 21 September), with integration packages and Workflows (2.24.1 to 2.26.1) publishing in between, so partial (12). 379 open issues and 1,291 open issues and pull requests on 6 November, with 241 issues opened in the 90 days to 3 November. Of the 50 newest, 28 had a comment and 3 were closed; a stale bot and an issue classifier run on the repository (12). Core, Workflows and integrations are current (15). CI and CodeQL passing on main and a stale-package policy that moves unmaintained integrations out of main (10). 20+12+12+15+10 = 69. | |||
| Transparency & trusteditorial 72, provenance 61checked 6 November 2026 | 7%8.8 | 5.9 | |
| MIT (30). The library stores nothing itself; OpenAI is the default provider unless changed, which the docs show (20). A stale-package policy and removals noted in the changelog, such as deprecated IPEX integrations removed in 0.14.25, without dated notice (10). No telemetry, though no page states it (12). 30+20+10+12 = 72. | |||
| Negative events | ≤15 |
| -2 |
| Total | 70 · BB | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 70 BB methodology v0.7
Fix list 16 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on LlamaIndex Framework. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- Reply times were sampled from comment counts on the 50 newest issues, not read issue by issue
- PyPI's project pages answered a bot check, so release dates come from the repository's changelog and tags
- The listing is named LlamaIndex Framework, the docs' own name, to keep it apart from the company and LlamaParse; the slug stays llamaindex
Sources 9
- repository (CHANGELOG, SECURITY.md, STALE.md, workflows, core source) github.com · seen 2026-11-06
- workflows-py repository and tags github.com · seen 2026-11-06
- llms.txt developers.llamaindex.ai · seen 2026-11-06
- agents guide developers.llamaindex.ai · seen 2026-11-06
- MCP guide developers.llamaindex.ai · seen 2026-11-06
- GHSA-488g-hw5f-x29p osv.dev · seen 2026-11-06
- OSV advisories for llama-index-core osv.dev · seen 2026-11-06
- PyPI downloads pypistats.org · seen 2026-11-06
- GitHub API, repository, issues and Actions runs api.github.com · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Free Free · OSS Free and open source under MIT. You pay for model calls. LlamaParse and LlamaCloud are separate paid services with their own Anchor Terminal listing.
Recent changes
- security.txt on llamaindex.ai is none, the listing says unknown source
- Latest release
Follow them as a feed at /feeds/tools/llamaindex.xml, or this listing's score history at history.json.
Get started
Install
pip install llama-index # MCP tools: pip install llama-index-tools-mcpAlternatives to LlamaIndex Framework
#11 of 20 in Best agent frameworks and SDKs · All 171 frameworks comparisons
AI SDK AAOpenAI Agents SDK AAPydantic AI AStrands Agents AMicrosoft Agent Framework AMastra BB
Head to head AgentOS vs LlamaIndex Framework · Agno vs LlamaIndex Framework · BoxLang AI vs LlamaIndex Framework · Claude Agent SDK vs LlamaIndex Framework · CrewAI vs LlamaIndex Framework · Cursor Agent SDK vs LlamaIndex Framework · Docker Agent vs LlamaIndex Framework · Agent Development Kit (ADK) vs LlamaIndex Framework · guilds.run vs LlamaIndex Framework · LangGraph vs LlamaIndex Framework · LlamaIndex Framework vs Mastra · LlamaIndex Framework vs Microsoft Agent Framework · LlamaIndex Framework vs OpenAI Agents SDK · LlamaIndex Framework vs Pydantic AI · LlamaIndex Framework vs smolagents · LlamaIndex Framework vs Strands Agents · LlamaIndex Framework vs TradingAgents · LlamaIndex Framework vs AI SDK
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| AI SDK Vercel Inc. | AA | 89.8 | agent.framework agent.mcp-client agent.multi-agent agent.durable | no |
| OpenAI Agents SDK OpenAI | AA | 86.2 | agent.framework agent.multi-agent agent.durable agent.mcp-client | no |
| Pydantic AI Pydantic | A | 81.9 | agent.framework agent.multi-agent agent.durable agent.mcp-client | no |
| Strands Agents Amazon Web Services | A | 80 | agent.framework agent.mcp-client agent.multi-agent agent.durable | no |
| Microsoft Agent Framework Microsoft | A | 79.4 | agent.framework agent.multi-agent agent.durable agent.mcp-client | no |
| Mastra Kepler Software, Inc. | BB | 74.2 | agent.framework agent.durable agent.mcp-client agent.multi-agent | no |
Machine-readable
- JSON
/api/v1/tools/llamaindex.json· historyhistory.json· badge/badges/llamaindex.svg· changes feed/feeds/tools/llamaindex.xml - Markdown
/tools/llamaindex.md· slim/tools/llamaindex.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/llamaindex.md·/fixes/llamaindex.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool llamaindex --md(the CLI) · over MCPget_tool {"slug": "llamaindex"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT llamaindex.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/llamaindex"><img src="https://www.anchorterminal.com/badges/llamaindex.svg" alt="LlamaIndex Framework on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/llamaindex)<a href="https://www.anchorterminal.com/tools/llamaindex">LlamaIndex Framework on Anchor Terminal</a>It counts on a page on llamaindex.ai or one of its subdomains, or the README at the root of github.com/run-llama/llama_index.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "llamaindex", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say LlamaIndex Framework is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/llamaindex. The logo is the one on this listing. If it's wrong or out of date, send us the right one.