Veryfi OCR for AI agents
Veryfi extracts structured data from receipts, invoices, and other financial documents, used by finance teams automating expense and bookkeeping data entry. 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 Veryfi OCR.
Process a document
Extract structured data, like totals and line items, from a receipt or invoice.
Search processed documents
Look up previously processed documents by vendor or date, a read-only search.
Confirm before deleting a document
Check with the user before deleting a processed document, since its extracted data goes with it.
5 Veryfi OCR actions, graded by risk.
Every Veryfi OCR action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- veryfi_ocr.get_documentGet Document
- veryfi_ocr.search_documentsSearch Documents
write
2Create and change things. Allow, or ask the user first.
- veryfi_ocr.update_documentUpdate Document
- veryfi_ocr.process_documentProcess Document
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- veryfi_ocr.delete_documentDelete Document
Veryfi OCR in three steps.
- 01Your users connect Veryfi OCRThey add their Veryfi OCR api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Document” can wait for the user, and “delete Document” can be denied outright.
- 03Any agent can actYour agent calls Veryfi OCR through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('veryfi_ocr', { read: 'allow', write: 'ask', // update_document destructive: 'deny', // delete_document }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Veryfi OCR connects.
Users add their Veryfi OCR 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 Veryfi OCR 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 Veryfi OCR from any agent.
Veryfi OCR and Arc0, answered.
Can I use Veryfi OCR with Claude, ChatGPT or Cursor?
Yes. Connect Veryfi OCR 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 Veryfi OCR actions you allow.
How do users connect Veryfi OCR?
Users add their Veryfi OCR 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 Veryfi OCR actions can my agent take?
5 in total: 2 read, 2 write and 1 destructive, such as “update Document”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Veryfi OCR?
Yes. Actions like “delete Document” 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 Veryfi OCR too?
Yes. The same Veryfi OCR connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Veryfi OCR into your agent.
Your users connect Veryfi OCR once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan