Credit spend explained
Dan Fletcher, engineering lead at Acme Ltd, asked how many credits parsing used this month. Memtro read the usage by day and tier. He saw where the spend went and took it to the budget meeting.
How many credits did parsing use this month, and which jobs failed?
LlamaCloud connects Memtro to your LlamaParse document processing project. It reads parse, extract and classify jobs with status, tier, errors and credits spent. It also reads managed indexes and pipelines with their sync state, files by type and expiry, and credit usage by day, event type or tier. When asked and granted, it can parse, extract from or classify a document, cancel or delete jobs, sync an index and delete indexes and files. LlamaCloud can also tell Memtro as jobs finish or fail, and a job can start on it. Parsed text and file names are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right LlamaCloud tool, reads what it needs, and answers with the source cited.
These tools change something in LlamaCloud. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in LlamaCloud, choosing the same kinds; the tab shows LlamaCloud's own steps. Each event can start a job, with the event as its input. LlamaCloud signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce LlamaCloud is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many credits did parsing use this month?
Which parse jobs failed this week, and why?
When was the contracts index last synced?
What document types did yesterday's classify jobs find?
Sync the contracts index now.
Dan Fletcher, engineering lead at Acme Ltd, asked how many credits parsing used this month. Memtro read the usage by day and tier. He saw where the spend went and took it to the budget meeting.
When a parse job failed at Northwind, LlamaCloud told Memtro and a job started. It read the job's status, tier and error and posted the cause for Sarah Chen, the data engineer. She fixed the source document and asked Memtro to parse it again.
The teams that lean on LlamaCloud most, a question each of them asks, and what they connect beside it.
A record in LlamaCloud is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In LlamaCloud, open the project Memtro should read, then API Key → Generate New Key. Copy it at once, since it is not shown again.
In Memtro, open Connections → LlamaCloud and paste the API key. Set the Region to eu if the account is on the EU host.
An administrator grants the actions by name, such as Parse a document, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then saved as a webhook configuration your code passes when it creates jobs.
Ask "How many credits did parsing use this month?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The LlamaCloud tools are the same everywhere.
Only when you ask, and only what it has been granted: parse a document from an uploaded file or public URL (spends credits per page); extract structured fields from a document (spends credits per page); classify a document against rules (spends credits); cancel a running parse, extract or classify job; delete a finished job and its results; sync an index, re-parsing changed files (spends credits); cancel an index's running sync; delete an index; delete a file. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In LlamaCloud, open the project Memtro should read, then API Key → Generate New Key. Copy it at once, since it is not shown again.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in LlamaCloud, choosing the same kinds; the tab shows LlamaCloud's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time