Install Jentic One Beta

Connect the TAGGUN Receipt OCR Scanning API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TAGGUN Receipt OCR Scanning API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftaggun.io%2Ftaggun" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftaggun.io%2Ftaggun" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with TAGGUN Receipt OCR Scanning API.

Add manually verified receipt data to a given receipt for feedback and training

Export a list of merchant names and addresses to normalise and match in CSV form

Import a list of merchant names and addresses to normalise and match in CSV to T

Query and filter TAGGUN Receipt OCR Scanning API records by parameters

GET STARTED

Start building with TAGGUN Receipt OCR Scanning API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TAGGUN Receipt OCR Scanning API for, with concrete tasks.

★ AI and Machine Learning Operations

Use the TAGGUN Receipt OCR Scanning API to perform ai ml operations programmatically. The API provides 25 endpoints covering core functionality including add manually verified receipt data to a given receipt for feedback and training , export a list of merchant names and addresses to normalise and match in csv form, import a list of merchant names and addresses to normalise and match in csv to t.

Call POST /api/account/v1/feedback to add manually verified receipt data to a given receipt for feedback and training

Automated Account Management

Automate account operations by combining multiple TAGGUN Receipt OCR Scanning API endpoints. Agents can export a list of merchant names and addresses to normalise and match in csv form and then import a list of merchant names and addresses to normalise and match in csv to t in a single workflow.

Call GET /api/account/v1/known-merchants/export to export a list of merchant names and addresses to normalise and match in csv form, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TAGGUN Receipt OCR Scanning API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'add manually verified receipt data to a given receipt for feedback and training ', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

25 endpoints — expects only running software, real reactions, and beautifully crafted apis to serve your every desire to transcribe a piece of paper to digital form.

METHOD

PATH

DESCRIPTION

POST

/api/account/v1/feedback

Add manually verified receipt data to a given receipt for feedback and training

GET

/api/account/v1/known-merchants/export

Export a list of merchant names and addresses to normalise and match in CSV form

POST

/api/account/v1/known-merchants/import

Import a list of merchant names and addresses to normalise and match in CSV to T

GET

/api/account/v1/known-product-codes/export

Export a list of product codes to normalise and match in CSV format

POST

/api/account/v1/known-product-codes/import

Import a list of product codes to normalise in and match in CSV to TSV format.

POST

/api/account/v1/merchantname/add

Add a keyword to your account's model to predict merchant name. Changes in your

GET

/api/account/v1/product-categories/export

Export a list of product categories and descriptions to match in CSV format

POST

/api/account/v1/product-categories/import

Import a list of product categories and descriptions to match in CSV to TSV form

POST

/api/account/v1/feedback

Add manually verified receipt data to a given receipt for feedback and training

GET

/api/account/v1/known-merchants/export

Export a list of merchant names and addresses to normalise and match in CSV form

POST

/api/account/v1/known-merchants/import

Import a list of merchant names and addresses to normalise and match in CSV to T

GET

/api/account/v1/known-product-codes/export

Export a list of product codes to normalise and match in CSV format

POST

/api/account/v1/known-product-codes/import

Import a list of product codes to normalise in and match in CSV to TSV format.

POST

/api/account/v1/merchantname/add

Add a keyword to your account's model to predict merchant name. Changes in your

GET

/api/account/v1/product-categories/export

Export a list of product categories and descriptions to match in CSV format

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the TAGGUN Receipt OCR Scanning API by hand means posting receipt and training payloads to its account endpoints and handling the import and export routes yourself. Through Jentic you install once, import the TAGGUN Receipt OCR Scanning API from the API Directory, and your agent calls it.

Permission scoping

TAGGUN's account operations carry their data in the request body, so limit the agent to the operations it needs, such as submitting feedback or exporting known merchants, rather than to any one resource. Every operation the agent can run is one you chose to allow, so imports that overwrite training data are excluded unless you add them.

Credential isolation

Any TAGGUN credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add verified receipt data for training' or 'export known merchants', and Jentic returns the matching TAGGUN operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TAGGUN Receipt OCR Scanning API through Jentic.

What authentication does the TAGGUN Receipt OCR Scanning API use?

The TAGGUN Receipt OCR Scanning API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I add manually verified receipt data to a given receipt for feedback and training with the TAGGUN Receipt OCR Scanning API?

Yes. Use the POST /api/account/v1/feedback endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the TAGGUN Receipt OCR Scanning API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I add manually verified receipt data to a given receipt for feedback and training through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add manually verified receipt data to a given receipt for feedback and training '. Jentic returns the matching TAGGUN Receipt OCR Scanning API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the TAGGUN Receipt OCR Scanning API have?

The TAGGUN Receipt OCR Scanning API exposes 25 endpoints covering account, receipt, validation operations.

Can I limit what my agent is allowed to do with the TAGGUN Receipt OCR Scanning API?

Yes. Because you run Jentic One yourself, your own rules decide which TAGGUN operations the agent may call and which credentials it may use. You can allow only the operations you need, such as POST /api/account/v1/feedback to submit verified receipt data or GET /api/account/v1/known-merchants/export to export merchant lists, while withholding others. Destructive operations like the import routes that overwrite training data stay excluded until you explicitly grant them.

TAGGUN Receipt OCR Scanning API

AI ReadinessAI-Aware (B)67/100

See full scorecard

AI/MLLanguage Modelsnone25 EndpointsREST

For Agents

Programmatically add manually verified receipt data to a given receipt for feedback and training , export a list of merchant names and addresses to normalise and match in csv form. Covers 25 operations.

Use for: I need to add manually verified receipt data to a given receipt for feedback and training , I want to export a list of merchant names and addresses to normalise and match in csv form, Search for import a list of merchant names and addresses to normalise and match in csv to t, Find all export a list of product codes to normalise and match in csv format

Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.

Expects only running software, real reactions, and beautifully crafted APIs to serve your every desire to transcribe a piece of paper to digital form. The API exposes 25 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

46%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

42%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

24%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TAGGUN Receipt OCR Scanning API to your agent

Capabilities

Start building with TAGGUN Receipt OCR Scanning API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

TAGGUN Receipt OCR Scanning API

Jentic AI Readiness Score

TAGGUN Receipt OCR Scanning API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness