LlamaParse
Parse PDFs, slides and scans into clean markdown and structured data with LlamaCloud.
Connect it with: API key. LlamaParse's own documentation: https://developers.llamaindex.ai/python/cloud/general/api_key/.
What agents can do
Connect LlamaParse so the agents working your tasks can reach it. With it connected, they can:
- Parse PDFs, Word and PowerPoint files, spreadsheets and scanned images into clean markdown or JSON, tables included.
- Extract structured fields from documents with LlamaExtract.
- Query your LlamaCloud indexes to answer questions from your own documents.
Before you start
- A LlamaCloud account (cloud.llamaindex.ai, or cloud.eu.llamaindex.ai for the EU region); the free plan includes monthly credits.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with LlamaParse
Jaah connects to LlamaParse with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: Sign in at cloud.llamaindex.ai, select API Key in the left sidebar, then Generate New Key; name it and select Create new key, then copy it at once (it is shown only once). It starts with llx-.
- API host: Keep https://api.cloud.llamaindex.ai for a North America account; use https://api.cloud.eu.llamaindex.ai when you signed in at cloud.eu.llamaindex.ai.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the LlamaParse card.
- Name the secret and choose who can use it.
- Fill in API key, API host.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to LlamaParse with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls LlamaParse's API once (GET <API host>/api/v1/projects) with the stored values, and shows whether LlamaParse accepted it, or which value LlamaParse refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key, base_url.
Tell the agent in your task description which secret to use, for example “use the LlamaParse secret org/llamaparse”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at LlamaParse once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at LlamaParse's side too, revoke or delete the key at LlamaParse.
Limitations
- A key works only in the region and project it was created in.
- Parsing spends LlamaCloud credits per page; the Test only lists your projects and spends none.
- Agents can do only what the connected LlamaParse account allows.
Troubleshooting
The Test says LlamaParse rejected the API key (401)
Most often the key belongs to the other region. If you signed in at cloud.eu.llamaindex.ai, set API host to https://api.cloud.eu.llamaindex.ai; otherwise create a new key under API Key and select Replace.
The Test passes but parsing fails with a credits error
The account's monthly credits are spent. Check Usage in LlamaCloud and upgrade or wait for the next period.
An agent cannot find documents it parsed earlier
Keys are tied to one project. Create the key in the project that holds the documents.
Still stuck? Select Test and read the result: it names the value LlamaParse refused and the status it answered.
FAQ
Is my data sent to the EU when I use the EU host?
Yes: with API host set to the EU address, every call from the agent goes to LlamaCloud's EU region.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one LlamaParse account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.