Upload a File and Let an Agent Read It
Create a files collection, upload a PDF, and have an agent find and read it over MCP. The agent gets the file's visible text and a verdict, never the original.
Prerequisites:
- A collection with at least one record. See Create a Collection.
- A Flux API connected to an agent. See Connect Claude.
- A PDF of a few pages, such as an invoice.
1. Create the files collection
Files belong to a parent record, so one customer's files stay with that customer.
- Open the owner collection, for example
customers. - In Subcollections, choose New subcollection.
- Choose Files, then Next.
- Name it
documents, keep Enable strict reference hierarchy on, and choose Create Collection.
In a project with GDPR mode on, the dialog first asks you to confirm that file data may be processed outside the EU. See Where file data lives.
2. Upload a file
Open a record, go to its Files tab, choose Upload files and pick the PDF. It moves through Uploading and Processing to one of:
| State | Meaning |
|---|---|
| Ready | Agents can read it. |
| In review | A finding held it for a reviewer. See Policy. |
| Rejected | Blocked or refused, with the reason. |
| Failed | Processing failed. |
Open the file to see its findings. Without table analysis, a 5-page PDF costs 6 file units: 5 pages and a verdict. See Billing & Usage.
3. Let an agent read it
Add the collection to your Flux API (how), connect your MCP client, and ask something the document answers: "What is the total on the Acme invoice?" The agent will:
- find the collection with
discover_resources; - find the matching pages with
search_records; - read the record with
get_record, addinginclude_linksfor page images.
The text arrives marked as untrusted, with the verdict and findings. The original is available only to people, through the dashboard or the Management API.
Next steps
- Agent-Ready Files — formats, verdicts, findings and downloads.
- Files Limits — sizes and rates.
- Multi-Tenant Agent Memory — keeping each customer's records apart.