Taggun
for LuumenAI
Read receipt data through Taggun, and correct the merchant list behind it
Taggun turns receipt and invoice images into structured fields: merchant, total, tax, date, line items. Luumen reads those results directly, along with the known merchant and product code lists your account matches against. When a merchant keeps resolving to the wrong name, the fix is an approved write, not a ticket to whoever holds the API key.
The Taggun toolbox
14 tools: 10 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadExport Known MerchantsExport the complete list of known merchants used for merchant name normalization in Taggun.
- ReadExport Known Product CodesExport the complete list of known product codes used for product normalization and matching in Taggun.
- ReadExport Product CategoriesExport a list of product categories and descriptions used for product categorization in CSV format.
- ReadGenerate Merchants CSVGenerate a CSV file with mock merchant data for testing purposes.
- ReadTranscribe Receipt from Base64 Encoded ImageExtract structured data from a receipt or invoice using base64 encoded image data.
- ReadTranscribe Receipt Encoded VerboseTranscribe a receipt using base64 encoded image in JSON payload and return detailed results.
- ReadTranscribe Receipt File (Simple)Upload a receipt or invoice image file and extract basic data including merchant name, total amount, tax amount, and date.
- ReadProcess Receipt via URLExtract structured data from a receipt or invoice image using OCR.
- ReadURL ValidationExtract and validate receipt data from a URL.
- ReadURL VerboseProcess a receipt or invoice from a URL for detailed data extraction.
- WriteAdd Merchant NameAdd a merchant name keyword to your account's model for predicting merchant names. Approval by default
- WriteImport Known MerchantsImport a list of merchant names and addresses to normalize and match in CSV or TSV format. Approval by default
- WriteImport Known Product CodesImport a list of product codes in CSV or TSV format for normalization and matching. Approval by default
- WriteImport Product CategoriesImport a list of product categories and descriptions for product categorization. Approval by default
One prompt, start to finish
What a governed Taggun run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add merchant name, import known merchants, import known product codes, import product categories — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Taggun — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Taggun to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.