Taggun
AI · AI
Receipts read from images, known merchants, product codes, and campaign validation on their own key.
Connect Taggun with Fabriq Developer
Your user pastes their Taggun credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Taggun in practice
Taggun caps the whole HTTP request body at 20 MiB and a PDF at 5 pages, returning 413 over either. The bigger surprise is that the fields an expense agent most wants are plan-gated rather than parameter-gated: duplicate, tampering, handwriting and digital-receipt detection start at the Advanced plan, and several fields have to be switched on in account settings before they are returned at all.
Scopes that draw scrutiny
apikey headerOne key, sent in an `apikey` header. Taggun’s instruction is to "store it in environment variables or a secrets manager — never in client-side code", because the key is the whole account.
Rate limits
- Over the limit the API returns 429 with the message "API rate limit exceeded" and the documented remedy "retry with exponential backoff". No requests-per-second figure is published.
- The complete HTTP request body is hard-capped at 20 MiB (20,971,520 bytes); over that the API returns 413.
- PDFs are limited to 5 pages.
- The trial is metered two ways at once: "the first 30 days or first 1,000 scans, whichever comes first, are free".
Worth knowing
- Accepted document types are JPEG, PNG (PNG8 and PNG24), GIF, HEIF, HEIC and PDF — HEIC support matters because that is what iPhones produce by default.
- 401 and 403 mean different things: 401 is a missing `apikey` header, 403 is a key that is present but invalid.
- A feature being "included on a plan" does not mean its fields come back — several have to be enabled in account settings first, so an empty field is not necessarily a failed extraction.
- Plans run Developer, Startup, Business, Advanced and Enterprise, and the fraud-detection suite plus receipt validation for promotions only appear from Advanced upward.
Checked against Getting started (2026-09-29), Document types and file requirements (2026-09-29), Errors (2026-09-29), API plans and features (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Taggun behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.