<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>LlamaParse changelog</title>
    <link>https://developers.llamaindex.ai/llamaparse/changelog/</link>
    <description>New features, improvements, and fixes across LlamaParse.</description>
    <language>en-us</language>
    <item>
      <title>Cap credit usage on a single project</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-09/#2026-09-01-per-project-credit-limits</link>
      <guid isPermaLink="false">2026-09-01-per-project-credit-limits</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:ui</category>
      <category>surface:api</category>
      <description>&lt;p&gt;Organization admins can now set a credit usage limit for an individual project, in
addition to the organization-wide limit. Once a project&amp;#39;s daily or monthly cap is
reached, its jobs are blocked until the period resets or the limit is raised. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/organizations/&quot;&gt;Organizations&lt;/a&gt; to set one.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sheets is deprecated</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-31-sheets-deprecated</link>
      <guid isPermaLink="false">2026-08-31-sheets-deprecated</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;The Sheets API is deprecated: it was removed from the SDKs in the 2026-08-28 release and
from the dashboard, and its docs moved to &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/deprecated/sheets/&quot;&gt;Deprecated&lt;/a&gt;.
Existing &lt;code&gt;/api/v1/sheets/&lt;/code&gt; integrations keep working but are unsupported; spreadsheets
are now handled by &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/supported_document_types/&quot;&gt;Parse&lt;/a&gt; and Extract&amp;#39;s
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/extract/guides/configuring-extract/#spreadsheet-mode&quot;&gt;spreadsheet mode&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Classify v1 removed from the API reference and SDKs</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-31-classify-v1-unpublished</link>
      <guid isPermaLink="false">2026-08-31-classify-v1-unpublished</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <category>classify</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <description>&lt;p&gt;The v1 Classify endpoints no longer appear in the API reference or new SDK releases.
Existing integrations keep working, but new development should use
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/classify/&quot;&gt;Classify&lt;/a&gt;, exposed in the SDKs as &lt;code&gt;client.classify&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>API key expiration in the dashboard</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-26-api-key-expiration</link>
      <guid isPermaLink="false">2026-08-26-api-key-expiration</guid>
      <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;Set an expiration when creating an API key. The API Keys page now shows expiry dates and
highlights keys expiring within seven days. See &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/api_key/&quot;&gt;API keys&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Index v2 opens to the free tier</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-20-index-v2-free-tier</link>
      <guid isPermaLink="false">2026-08-20-index-v2-free-tier</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <category>index</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;Index v2, with a redesigned dashboard for creating indexes, watching syncs, and testing
retrieval, is now available on every plan, including free. See the
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/cloud-index-v2/getting_started/&quot;&gt;getting started guide&lt;/a&gt; if you used the
previous Index.&lt;/p&gt;</description>
    </item>
    <item>
      <title>LlamaParse SDK for .NET</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-14-dotnet-sdk</link>
      <guid isPermaLink="false">2026-08-14-dotnet-sdk</guid>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:sdk</category>
      <description>&lt;p&gt;LlamaParse now has an official .NET SDK, published on NuGet as the
&lt;a href=&quot;https://www.nuget.org/packages/LlamaCloud/1.5.1&quot;&gt;&lt;code&gt;LlamaCloud&lt;/code&gt;&lt;/a&gt; package. It covers the
same surface as the Python and TypeScript SDKs for parsing, extracting, and classifying
documents from C# and F#.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bounding boxes for enriched forms</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-13-enriched-forms-bounding-boxes</link>
      <guid isPermaLink="false">2026-08-13-enriched-forms-bounding-boxes</guid>
      <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
      <category>parse</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;Enriched forms, still in beta, now return field-level bounding boxes to help locate and
verify extracted values. No new setting or added cost; available in the API and SDKs,
and in the dashboard on paid plans. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/parse/examples/enriched_forms/&quot;&gt;Enriched forms&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Turbo tier for Extract</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-12-extract-turbo-tier</link>
      <guid isPermaLink="false">2026-08-12-extract-turbo-tier</guid>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category>extract</category>
      <category>surface:api</category>
      <description>&lt;p&gt;Turbo is now available in beta through the Extract API, offering lower latency with
accuracy comparable to Agentic. Single-page documents with simple schemas can complete
in as little as three seconds.&lt;/p&gt;
&lt;p&gt;It has no parse output or bounding boxes; limited support for citations and confidence
scores. See &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/extract/guides/configuring-extract/#tiers&quot;&gt;tiers&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>MCP endpoint for the EU region</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-08/#2026-08-06-eu-mcp-endpoint</link>
      <guid isPermaLink="false">2026-08-06-eu-mcp-endpoint</guid>
      <pubDate>Thu, 06 Aug 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:api</category>
      <description>&lt;p&gt;EU accounts can now connect agents to their regional LlamaParse deployment through MCP.
The MCP configuration shown in the console points at your account&amp;#39;s region
automatically. See &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/regions/&quot;&gt;Regions&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Extract's agentic plus tier is generally available</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-07/#2026-07-22-extract-agentic-plus-ga</link>
      <guid isPermaLink="false">2026-07-22-extract-agentic-plus-ga</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <category>extract</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;Built for long documents, dense tables, and large schemas, &lt;code&gt;agentic_plus&lt;/code&gt; is now
generally available on every plan. It supports schemas up to 3,200 fields at a premium
rate, and returns confidence scores and citations. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/extract/#tiers-and-versions&quot;&gt;tiers and versions&lt;/a&gt; and
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/pricing/#extraction&quot;&gt;pricing&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enriched forms parsing</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-07/#2026-07-22-enriched-forms-parsing</link>
      <guid isPermaLink="false">2026-07-22-enriched-forms-parsing</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <category>parse</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <description>&lt;p&gt;Parse can now return a forms-specific output when it detects a form on a page, tuned
first on common tax forms. This is in beta and costs an additional 10 credits per page
where a form is found. See &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/parse/examples/enriched_forms/&quot;&gt;Enriched forms&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>High-effort confidence scores for Parse</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-07/#2026-07-15-parse-confidence-score-effort</link>
      <guid isPermaLink="false">2026-07-15-parse-confidence-score-effort</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>parse</category>
      <category>surface:api</category>
      <category>surface:ui</category>
      <description>&lt;p&gt;Parse can now grade its own output with an additional review pass, returning
page-level confidence scores and a document-level summary. It costs an additional 5
credits per page and is available in the API and the playground. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/parse/guides/configuring-parse/#confidence-score-high-effort&quot;&gt;Configuring Parse&lt;/a&gt;
for how to turn it on.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Per-product MCP endpoints</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-06/#2026-06-30-mcp-per-product-endpoints</link>
      <guid isPermaLink="false">2026-06-30-mcp-per-product-endpoints</guid>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:api</category>
      <description>&lt;p&gt;The LlamaParse MCP server now covers Extract and Index alongside Parse, Classify, and
Split, with a scoped endpoint per product. This lets an agent get access to just the
part of the platform it needs, and run several in parallel. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/for-agents/mcp/&quot;&gt;MCP&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Usage tags for billing attribution</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-06/#2026-06-29-usage-tags</link>
      <guid isPermaLink="false">2026-06-29-usage-tags</guid>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:api</category>
      <description>&lt;p&gt;Enterprise organizations can now tag parse and extract requests with custom labels,
carried through to usage metrics. This lets billing data be sliced by team,
environment, or customer. See &lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/general/usage_tags/&quot;&gt;Usage tags&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Label parse jobs with your own metadata</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-06/#2026-06-29-parse-user-metadata</link>
      <guid isPermaLink="false">2026-06-29-parse-user-metadata</guid>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <category>parse</category>
      <category>surface:api</category>
      <category>surface:sdk</category>
      <description>&lt;p&gt;Parse jobs now accept a &lt;code&gt;user_metadata&lt;/code&gt; object at creation, for whatever context your
application needs to keep with the job. It&amp;#39;s returned unchanged on every get and list
response, and can&amp;#39;t be changed after the job is created. See
&lt;a href=&quot;https://developers.llamaindex.ai/llamaparse/parse/guides/configuring-parse/&quot;&gt;Configuring Parse&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Go, Java, and CLI SDKs</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-06/#2026-06-26-go-java-cli-sdks</link>
      <guid isPermaLink="false">2026-06-26-go-java-cli-sdks</guid>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <category>platform</category>
      <category>surface:sdk</category>
      <description>&lt;p&gt;LlamaParse now ships official SDKs for Go and Java, plus a command-line client,
alongside the existing Python and TypeScript SDKs. All are generated from the same API
definition, so they share the same surface and stay in step with new releases. See the
&lt;a href=&quot;https://developers.llamaindex.ai/reference/&quot;&gt;API reference&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Parse jobs can use a saved configuration</title>
      <link>https://developers.llamaindex.ai/llamaparse/changelog/2026-06/#2026-06-17-parse-saved-configurations</link>
      <guid isPermaLink="false">2026-06-17-parse-saved-configurations</guid>
      <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
      <category>parse</category>
      <category>surface:api</category>
      <description>&lt;p&gt;The parse API now accepts a &lt;code&gt;configuration_id&lt;/code&gt;, so a saved configuration can be applied
to a job directly instead of repeating every option in the request. The other APIs
already supported this; Parse now matches them. See the
&lt;a href=&quot;https://developers.llamaindex.ai/reference/resources/parsing/methods/create/&quot;&gt;parse request reference&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
