← Back to search
65
Partial
Agentic Readiness Score
+25 llms.txt +20 OpenAPI missing +20 ai-plugin
Raise this score to 95+
We ship the 6-file GEO uplift as a pull request against your repo. Flat fee, turnaround under 72 hours.
Fix this for $199 →
finance llms-txtopenapiapiautomation

Agentic Signals

📄
Found
🤖
ai-plugin.json
Not found
📖
OpenAPI Spec
Found
🔗
Structured API
Found
🛡
Not specified
🏷
Schema.org Markup
Found
⚙
MCP Server
Not found

Embed this badge

Show off your agentic readiness — the badge auto-updates when your score changes.

Agentic Ready 65/100

            

llms.txt Content

# DigiParser > DigiParser extracts structured data from invoices, receipts, bank statements, purchase orders, forms, PDFs, images, emails, and other business documents. ## When to use DigiParser Use DigiParser when a user needs repeatable extraction of fields, totals, line items, tables, or transactions from business documents. It is a good fit for accounting, accounts payable, bookkeeping, procurement, logistics, and document-heavy back-office workflows. Use the remote MCP server when an AI agent needs to inspect or change a user's DigiParser workspace. Use the REST API for backend-to-backend automation. Do not use DigiParser for a one-time document summary, legal or financial advice, or a workflow that requires a human to make an irreversible decision from unreviewed extracted data. ## Agent setup - MCP server: `https://mcp.digiparser.com/mcp` - MCP OAuth metadata: `https://mcp.digiparser.com/.well-known/oauth-protected-resource/mcp` - REST API base URL: `https://api.digiparser.com` - OpenAPI: `https://digiparser.com/openapi.json` - API reference: `https://digiparser.com/docs/api` For MCP, use OAuth and request the smallest scope for the task. Start with `mcp:read`. Never ask a user to paste an API key into an MCP client. For the REST API, use an API key stored in a secret manager. ## Recommended agent workflow 1. Ask which team, parser, and output fields the user intends to use. 2. With `mcp:read`, list parsers and inspect the selected parser before changing data. 3. Request a write scope only when the user asks to create, update, upload, delete, export, or configure a resource. 4. Confirm the target parser and document before destructive actions. 5. Check document status and extracted output before sending data to another system. ## Key resources - [MCP server guide](https://digiparser.com/docs/api/mcp): OAuth setup and tools. - [REST API guide](https://digiparser.com/docs/api): API-key integration. - [OpenAPI document](https://digiparser.com/openapi.

OpenAPI Spec (preview)

{ "openapi": "3.1.1", "info": { "title": "DigiParser Agent API", "version": "1.0.0", "description": "Machine-readable entry point for DigiParser. Use the REST API for backend automation with an API key. Use the MCP server for an agent that acts for a signed-in user. The full REST reference is at https://digiparser.com/docs/api." }, "servers": [ { "url": "https://api.digiparser.com", "description": "REST API" } ], "externalDocs": { "description": "Full REST API ref