Integration

TAGGUN integration

TAGGUN is a receipt and invoice OCR API. Scan a receipt image or PDF, from a stored file or a public HTTPS URL, and get the total, tax, date and merchant back (simple), or those plus line items, detailed merchant data and fraud signals (verbose). It also validates receipts for promotions: against rules sent with the request (beta), or against a stored campaign whose rules you create, read, replace and delete. Not included: the base64 encoded-file variants, the campaign ID list (a bare list of strings), and the CSV import and export of reference data. Authentication is an API key sent in the apikey header.

Connect TAGGUN How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TAGGUN.Built from the 12 TAGGUN tools below, on the connection you add once.

What you can do with TAGGUN

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

File, 4 operations

scan_receipt_fileScan receipt filePOSTScans a stored receipt or invoice file (image or PDF) and returns the core fields: total amount, tax amount, date and merchant name and address, each with a confidence level.
scan_receipt_file_verboseScan receipt file verbosePOSTScans a stored receipt or invoice file and returns the verbose extraction: core fields plus product line items, detailed merchant data, helper arrays, per-field metadata and account-enabled feature results.
validate_receipt_file_for_campaignValidate receipt file for campaignPOSTValidates a stored receipt file against the rules saved for a campaign (create_campaign_settings) and returns pass or fail with the passed and failed rule keys, matched line items and fraud signals.
validate_receipt_file_with_rulesValidate receipt file with rulesPOSTValidates a stored receipt file against rules sent with this request (no stored campaign) and returns pass or fail with the passed and failed rule keys and the extracted values. Beta, must be enabled on the account.

Url, 4 operations

scan_receipt_urlScan receipt urlPOSTScans a receipt or invoice hosted at a public HTTPS URL and returns the core fields: total amount, tax amount, date and merchant name and address, each with a confidence level.
scan_receipt_url_verboseScan receipt url verbosePOSTScans a receipt or invoice hosted at a public HTTPS URL and returns the verbose extraction: core fields plus product line items, detailed merchant data, helper arrays and per-field metadata.
validate_receipt_url_for_campaignValidate receipt url for campaignPOSTValidates a receipt at a public HTTPS URL against the rules saved for a campaign (create_campaign_settings) and returns pass or fail with the passed and failed rule keys, matched line items and fraud signals.
validate_receipt_url_with_rulesValidate receipt url with rulesPOSTValidates a receipt at a public HTTPS URL against rules sent with this request (no stored campaign) and returns pass or fail with the passed and failed rule keys and the extracted values. Beta, must be enabled on the account.

Create, 1 operation

create_campaign_settingsCreate campaign settingsPOSTCreates the validation rules for a new campaign ID: date window, merchant names, product codes, product line items, balance owing, fraud checks and SmartValidate prompts. Include only the sections to evaluate.

Delete, 1 operation

delete_campaign_settingsDelete campaign settingsDELETEDeletes the validation rules stored for a campaign; later validations against that campaign ID can no longer use them. Delete only after the campaign's submission window has closed.

Setting, 1 operation

get_campaign_settingsGet campaign settingsGETReturns the validation rules stored for a campaign. Empty rule sections may be omitted. To change them, edit this result and pass it to update_campaign_settings.

Update, 1 operation

update_campaign_settingsUpdate campaign settingsPUTReplaces the whole rule set stored for a campaign: sections left out are removed. Read the current rules with get_campaign_settings first, edit them, then send every section that should stay active.

Use TAGGUN from Claude Code, Cursor or Codex

Connect TAGGUN in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TAGGUN operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TAGGUN

Create your workspace
Sign up free. Nothing to install.
Connect TAGGUN once
Add your TAGGUN connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.