Install Jentic One Beta

Connect the TIPO Open Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TIPO Open Data 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%2Fcloud.tipo.gov.tw%2Ftipo" | 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%2Fcloud.tipo.gov.tw%2Ftipo" | 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 TIPO Open Data API.

Search Taiwan patent records by keyword, applicant, or patent number

Retrieve a single patent record by its TIPO patent number

List patent gazette publications and filter by publication period

Search Taiwan trademark records by keyword or applicant

Download bulk gazette resource files by resource ID

GET STARTED

Start building with TIPO Open Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TIPO Open Data API for, with concrete tasks.

★ IP Watch and Competitive Monitoring

Monitor Taiwan patent and trademark filings for a competitor or technology area by polling the search endpoints on a schedule. /api/patent/search and /api/trademark/search accept keyword and applicant filters, which is enough signal to drive a daily IP watch report for legal teams covering the Taiwan market. New filings can be deduplicated against the patent number returned by /api/patent/{patentNo}.

Call /api/patent/search with a competitor's company name and a publication date filter for the past 30 days, then return the new patent numbers

Gazette Ingestion for Legal Databases

Pull TIPO patent gazette data into a commercial IP database. /api/patent/gazette lists gazette publications and /api/download/{resourceId} fetches the underlying resource file for archival, which is the standard ingestion pattern for IP analytics vendors that resell Taiwan data. The pipeline can be re-run on each gazette release to keep the downstream database current.

List gazette publications via /api/patent/gazette since the last run, then call /api/download/{resourceId} for each new entry

Trademark Clearance Searches

Run a quick clearance search before filing a new trademark in Taiwan by querying /api/trademark/search for the proposed mark. Results return matching registered marks and pending applications, which lets a legal assistant flag conflicts before the client commits to a brand. Combined with TIPO's gazette listings, this creates a low-cost first-pass clearance tool.

Call /api/trademark/search with the proposed mark string and return any registered Taiwan trademarks that match

Open-Data Research Aggregation

Aggregate TIPO open-data resources into a research portal alongside other government datasets. /opdata exposes the catalogue listing and /api/download/{resourceId} retrieves individual resource files, which is enough to wire TIPO into a multi-source open-data dashboard. This is the typical pattern for academic IP research and journalism.

Call /opdata to list available TIPO datasets and download the most recent patent statistics resource

Agent-Driven IP Lookups via Jentic

AI assistants used by patent attorneys and analysts can answer 'has this idea already been filed in Taiwan?' by searching Jentic for an intent like 'search taiwan patents' and executing /api/patent/search behind the scenes. The TIPO API key lives in your Jentic One instance and never enters the agent's logs, which matters for law firms with strict client confidentiality controls.

Search Jentic for 'search taiwan patents', load /api/patent/search, and execute with the user's keyword

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for tipo open data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/patent/search

Search Taiwan patents

GET

/api/patent/{patentNo}

Get a patent by patent number

GET

/api/patent/gazette

List patent gazette publications

GET

/api/trademark/search

Search Taiwan trademarks

GET

/api/download/{resourceId}

Download a resource by ID

GET

/opdata

List the open-data catalogue

GET

/api/patent/search

Search Taiwan patents

GET

/api/patent/{patentNo}

Get a patent by patent number

GET

/api/patent/gazette

List patent gazette publications

GET

/api/trademark/search

Search Taiwan trademarks

GET

/api/download/{resourceId}

Download a resource by ID

GET

/opdata

List the open-data catalogue

Why Jentic?

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

Setup

Wiring the TIPO Open Data API by hand means passing its apikey as a query parameter, reverse-engineering its patent and trademark endpoints off an open-data portal, and handling retries yourself against cloud.tipo.gov.tw/S220. Through Jentic you install once, import the TIPO Open Data API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The TIPO Open Data API is read-only, with the patent number carried in the URL path (/api/patent/{patentNo}), so scope the agent to the operations it needs, such as searching patents or fetching a patent by number. You choose which operations are in that set, so it stays limited to the read operations you allow.

Credential isolation

Your TIPO API key is stored once, encrypted, by your own Jentic One instance and injected as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search Taiwan patents' or 'get a patent by number', and Jentic returns the matching TIPO operation with its query schema, so the agent calls the right endpoint without reverse-engineering the open-data portal.

FAQs

Specific to using TIPO Open Data API through Jentic.

Why is there no official OpenAPI spec for TIPO Open Data API?

Taiwan Intellectual Property Office does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call TIPO Open Data API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the TIPO Open Data API use?

TIPO uses an apiKey scheme - the key is passed as the apikey query parameter. Some endpoints accept anonymous access; others require a key issued by the TIPO open data portal. Through Jentic, the apikey is stored in the vault and injected per call so it never enters the agent's context.

Can I search Taiwan trademarks with this API?

Yes. GET /api/trademark/search accepts keyword and applicant filters and returns matching Taiwan trademark records, which is enough to drive a clearance lookup or competitive monitoring report.

What are the rate limits for the TIPO Open Data API?

TIPO does not publish a formal rate limit in this spec. Treat the service as best-effort government infrastructure - back off on 429 or 503 responses and avoid bursting more than a few requests per second per API key.

How do I look up a Taiwan patent by number through Jentic?

Run pip install jentic, search for 'get taiwan patent by number', load the /api/patent/{patentNo} operation, then execute with the patent number. The call returns the gazette record for that patent.

Can I download bulk gazette files with this API?

Yes. GET /api/download/{resourceId} returns the underlying gazette resource by its ID, and resource IDs come from the gazette listing at /api/patent/gazette or the catalogue at /opdata.

Can I limit what my agent is allowed to do with the TIPO Open Data API?

Yes. Because you run Jentic One yourself, your own rules decide which TIPO operations the agent may call, so you can allow read-only lookups like GET /api/patent/search and GET /api/patent/{patentNo} while withholding trademark search, gazette listing, or bulk downloads via GET /api/download/{resourceId}. The whole API is read-only, so nothing the agent runs can create or change TIPO records. You also control the apikey credential, which your Jentic One instance injects only for the operations you have permitted.

Cloud Tipo TIPO Open Data API

AI ReadinessFoundational (D+)49/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search Taiwan patents and trademarks, retrieve patent gazette records, and download TIPO open-data resources by ID.

Use for: I need to search Taiwan patents that mention a specific keyword, Retrieve the gazette record for a specific Taiwan patent number, List the most recent patent gazette publications from TIPO, Search Taiwan trademarks owned by a particular applicant

Not supported: Does not handle patent filing, prosecution, or non-Taiwan jurisdictions - use for read-only access to TIPO patent and trademark gazette data only.

Jentic publishes the only available OpenAPI specification for TIPO Open Data API, keeping it validated and agent-ready. The Taiwan Intellectual Property Office (TIPO) Open Data API exposes patent and trademark gazette data published by the Taiwan government, including patent search, individual patent records, gazette listings, and trademark search. It also exposes a generic open-data listing endpoint and a resource download endpoint for bulk gazette files. Some endpoints work without an API key, and others require the apikey query parameter issued by TIPO's open data portal.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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).

100%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

58%

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: C-Signals: 4

50%

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.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TIPO Open Data API to your agent

Capabilities

Start building with TIPO Open Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cloud Tipo TIPO Open Data API

Jentic AI Readiness Score

TIPO Open Data 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