Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

AI Tools

Receipt & Invoice OCR Recognition

Extract key information from receipt/invoice images and convert to custom JSON format using AI vision models

json· JSON resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL
# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/ai-image-to-receipt-json' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"imageFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/ai-image-to-receipt-json' \
  -F 'imageFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'jsonFormat=输入自定义的JSON格式结构，例如：
{
  "merchantName": "string or null",
  "totalAmount": "number or null",
  "date": "string (YYYY-MM-DD) or null",
  "items": [
    {
      "name": "string or null",
      "price": "number or null"
    }
  ]
}'

© 2026 Elysia Tools. Developer documentation.

Back to siteBrowse tools

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP
POST https://api.elysiatools.com/en/api/tools/ai-image-to-receipt-json

Parameters

NameTypeRequiredDescription
imageFilefileupload requiredYesSupports receipt/invoice photos in common image formats such as JPG, PNG, WebP
jsonFormattextareaNoLeave empty to use default format, or enter custom JSON structure to specify fields to extract
File-type parameters must be uploaded first via POST /upload/ai-image-to-receipt-json, then the returned filePath is passed to the corresponding file field.

Response format

JSON result

JSON
{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json
{
  "mcpServers": {
    "elysiatools-ai-image-to-receipt-json": {
      "name": "ai-image-to-receipt-json",
      "description": "Extract key information from receipt/invoice images and convert to custom JSON format using AI vision models",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=ai-image-to-receipt-json",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "ai-image-to-receipt-json",
    "arguments": {
  "imageFile": "https://example.com/file.ext",
  "jsonFormat": "输入自定义的JSON格式结构，例如：\n{\n  \"merchantName\": \"string or null\",\n  \"totalAmount\": \"number or null\",\n  \"date\": \"string (YYYY-MM-DD) or null\",\n  \"items\": [\n    {\n      \"name\": \"string or null\",\n      \"price\": \"number or null\"\n    }\n  ]\n}"
}
  }
}
Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).
File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]

Browse tools
Open tool