OCR Web Service for AI agents
OCR Web Service offers SOAP and REST APIs for adding optical character recognition to software, mobile apps, and web services. Developers use it to extract text from scanned images and documents. 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 OCR Web Service.
Recognize text in a scanned file
Run OCR recognition on a scanned document to produce editable, searchable text.
Check account usage read-only
Look up account information and credentials before running a batch of recognition jobs.
Review the recognition log
Pull the OCR service log to confirm a batch of jobs completed as expected.
4 OCR Web Service actions, graded by risk.
Every OCR Web Service 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.
- ocr_web_service.get_account_credentialsGet Account Credentials
- ocr_web_service.get_account_informationGet Account Information
write
2Create and change things. Allow, or ask the user first.
- ocr_web_service.logOCR Web Service Log
- ocr_web_service.recognizeOCRWebService Recognize
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
OCR Web Service in three steps.
- 01Your users connect OCR Web ServiceThey add their OCR Web Service username and password on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “oCR Web Service Log” can wait for the user to approve.
- 03Any agent can actYour agent calls OCR Web Service through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ocr_web_service', { read: 'allow', write: 'ask', // log destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How OCR Web Service connects.
Users add their OCR Web Service username and password 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 OCR Web Service 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
- Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use OCR Web Service from any agent.
OCR Web Service and Arc0, answered.
Can I use OCR Web Service with Claude, ChatGPT or Cursor?
Yes. Connect OCR Web Service 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 OCR Web Service actions you allow.
How do users connect OCR Web Service?
Users add their OCR Web Service username and password 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 OCR Web Service actions can my agent take?
4 in total: 2 read, 2 write and 0 destructive, such as “oCR Web Service Log”. Your policies decide which of them each agent may call.
Can I make my agent read-only in OCR Web Service?
Yes. Allow read actions and deny writes in the OCR Web Service policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call OCR Web Service too?
Yes. The same OCR Web Service connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug OCR Web Service into your agent.
Your users connect OCR Web Service once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan