Eagle Doc MCP integration for AI agents.
Connect AI agents to Eagle Doc through 5 structured actions, including get current usage, process finance document, and get quota. Review authentication, inp…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Eagle Doc integration exposes
The Eagle Doc Agent App exposes 5 provider-backed actions for ai, finance, and productivity work. Its current contract lets an authorized agent fetch the current billing-month usage counters for the connected eagle doc api key, upload one invoice, receipt, or pdf to eagle doc finance ocr and return the structured extraction result, and fetch the overall eagle doc management quota summary tied to the connected api key. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Eagle Doc account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Eagle Doc capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_usageREADFetch the current billing-month usage counters for the connected Eagle Doc API key.
process_finance_documentREVIEWUpload one invoice, receipt, or PDF to Eagle Doc Finance OCR and return the structured extraction result.
INPUTS: contentBase64 / fileName / mimeType / privacy / polygon
get_quotaREADFetch the overall Eagle Doc management quota summary tied to the connected API key.
list_monthly_usageREADList Eagle Doc monthly usage history together with pricing metadata for each month returned.
list_usage_logsREADList recent Eagle Doc request log rows with processed page counts and timestamps.
INPUT CONTRACTS
Know what the action needs before it runs.
process_finance_document
contentBase64REQUIRED- The Base64-encoded content of the uploaded invoice, receipt, image, or PDF.
fileNameREQUIRED- The file name sent to Eagle Doc for the uploaded document.
mimeTypeOPTIONAL- The MIME type sent to Eagle Doc for the uploaded document.
privacyOPTIONAL- Whether Eagle Doc should avoid storing the uploaded file on the server. Eagle Doc defaults this to true.
polygonOPTIONAL- Whether Eagle Doc should include polygon coordinates for extracted fields.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Usage
Fetch the current billing-month usage counters for the connected Eagle Doc API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_usageVerify with Get Quota
Fetch the overall Eagle Doc management quota summary tied to the connected API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_quotaSAFETY BOUNDARY
Operate Eagle Doc with explicit limits
- Authorize Eagle Doc with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Eagle Doc data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Eagle Doc rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Eagle Doc task completed successfully.
CONNECTION MODEL
API key
Eagle Doc API key sent with the api-key header. Subscribe and sign in to the Eagle Doc API dashboard to copy it.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Eagle Doc.