Eagle doc
for LuumenAI
Read invoices and receipts, check quota, submit batch OCR jobs on approval
Eagle Doc turns invoices, receipts, and mixed document piles into structured JSON. Connect it and Luumen can pull fields from a single image on the spot, check how much of your monthly quota is left, and read request logs when a run looks off. Batch jobs are submitted as a previewed, approved step.
The Eagle doc toolbox
9 tools: 7 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadProcess Any Document with OCRProcess any document type with OCR and automatic classification.
- ReadEagle Doc Invoice OCR from Base64Extract invoice data from base64 encoded images using Eagle Doc OCR API.
- ReadGet Management QuotaGet contractual quota allowance and current usage counters for all workloads.
- ReadReceipt OCR V3Process receipt images into structured JSON with 40+ fields including merchant info, line items, taxes, and payments.
- ReadGet Current Month UsageGet current month's usage statistics including quota, pages processed, over-usage, and costs.
- ReadGet Monthly Usage HistoryRetrieve historical monthly usage data with pricing context for reconciliation and forecasting.
- ReadGet Usage Request LogsRetrieve chronological list of recent API calls with page counts and timestamps.
- WriteSubmit Batch Any Document OCR TaskSubmit batch OCR processing tasks for various document types including bank statements, resumes, passports, delivery sheets, and more. Approval by default
- WriteDelete Batch Processing TaskDelete a submitted batch processing task from the queue. Approval by default
One prompt, start to finish
What a governed Eagle doc run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as submit batch any document ocr task, delete batch processing task. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Eagle doc — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Eagle doc to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.