Invofox for AI agents
Invofox extracts structured data and OCR text from invoices and other business documents to support document workflows. Office and operations staff use it to keep documents moving without manual reformatting. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Invofox.
Process an invoice by URL
Submit an invoice document URL for OCR processing to extract line items and totals.
Check a document's extracted text
Pull the extracted text of a processed document to verify accuracy before it is filed.
Update a document's state
Mark a document as reviewed only after someone confirms the extracted data is correct.
10 Invofox actions, graded by risk.
Every Invofox action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- invofox.get_importGet Import
- invofox.get_documentGet Document
- invofox.list_companiesList Companies
- invofox.list_documentsList Documents
- invofox.get_document_textGet Document Text
write
4Create and change things. Allow, or ask the user first.
- invofox.create_companyCreate Company
- invofox.update_documentUpdate Document
- invofox.set_document_stateSet Document State
- invofox.process_documents_by_urlProcess Documents by URL
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- invofox.delete_companyDelete Company
Invofox in three steps.
- 01Your users connect InvofoxThey add their Invofox api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Company” can wait for the user, and “delete Company” can be denied outright.
- 03Any agent can actYour agent calls Invofox through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('invofox', { read: 'allow', write: 'ask', // create_company destructive: 'deny', // delete_company }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Invofox connects.
Users add their Invofox api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Invofox connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Invofox from any agent.
Invofox and Arc0, answered.
Can I use Invofox with Claude, ChatGPT or Cursor?
Yes. Connect Invofox to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Invofox actions you allow.
How do users connect Invofox?
Users add their Invofox api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Invofox actions can my agent take?
10 in total: 5 read, 4 write and 1 destructive, such as “create Company”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Invofox?
Yes. Actions like “delete Company” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Invofox too?
Yes. The same Invofox connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Invofox into your agent.
Your users connect Invofox once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan