Install Jentic One Beta

Connect the WTO Timeseries API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WTO Timeseries 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%2Fapiportal.wto.org%2Fwto-timeseries" | 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%2Fapiportal.wto.org%2Fwto-timeseries" | 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 WTO Timeseries API.

List the trade and tariff indicators available in the dataset

List reporting and partner economies and territory regions

List product classifications and individual products

List available time periods, frequencies, and years

Retrieve numeric trade statistics time series for a query

GET STARTED

Start building with WTO Timeseries API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use WTO Timeseries API for, with concrete tasks.

★ Build trade statistics dashboards

Analysts building dashboards need consistent, sourced trade figures. The WTO Timeseries API lists the available indicators and economies and returns the numeric series for a chosen query, so a dashboard can pull tariff and trade-flow data straight from the source.

Retrieve the annual export values for a chosen economy and present them as a series.

Discover the dataset structure before querying

Trade data queries need valid indicator, economy, and product codes. The API lists indicators, reporting and partner economies, product classifications, and time periods, letting an integration resolve the right codes before it requests the numbers.

List the indicators and reporting economies so a user can pick a valid combination.

Feed trade data into research models

Economic research pipelines ingest official trade series over time. The API returns the numeric data for an indicator, economy, and product across the covered years, so a pipeline can pull a clean series for modelling or comparison.

Retrieve a trade indicator series for two economies across all available years.

Let an agent answer trade-data questions

An AI agent fielding trade or economics questions can resolve the right codes and fetch the numbers itself. Through Jentic the agent discovers the metadata and data operations by intent and runs them under the integration's subscription key, returning a sourced answer.

Given two economies, find the right indicator and return their trade values over time.

Key Endpoints

14 endpoints — the wto timeseries api serves international trade and tariff statistics published by the world trade organization over a rest interface.

METHOD

PATH

DESCRIPTION

GET

/indicators

List the available trade and tariff indicators

GET

/reporters

List the reporting economies

GET

/partners

List the partner economies

GET

/products

List products in the classifications

GET

/data

Retrieve the numeric trade statistics time series

GET

/years

List the years covered by the dataset

GET

/topics

List the topics that group indicators

GET

/indicators

List the available trade and tariff indicators

GET

/reporters

List the reporting economies

GET

/partners

List the partner economies

GET

/products

List products in the classifications

GET

/data

Retrieve the numeric trade statistics time series

GET

/years

List the years covered by the dataset

GET

/topics

List the topics that group indicators

Why Jentic?

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

Setup

Querying WTO data yourself means learning the indicator, economy, and product codes, tracking the subscription key, and chaining metadata calls before the data call. With Jentic you install once, import WTO Timeseries from the Directory, and store the subscription key a single time.

Permission scoping

Running Jentic in your own instance, you decide which WTO Timeseries operations the agent may call, so you can allow metadata and data reads while keeping the surface narrow. Access is granted per operation.

Credential isolation

Your WTO subscription key is held encrypted by your own Jentic One instance and injected only when a call runs, so it never appears in the agent's prompt, logs, or context.

Intent-based discovery

Agents find WTO Timeseries through Jentic's intent search: a request like get export values between two economies resolves to the right operation with inputs and auth prepared.

FAQs

Specific to using WTO Timeseries API through Jentic.

Is there an MCP server for the WTO Timeseries API?

You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call WTO Timeseries operations directly by intent, so you connect the API without maintaining separate MCP tooling.

Can I limit which WTO Timeseries operations my agent can call?

Yes. Because you run Jentic yourself, you choose which WTO Timeseries operations your agent can call, so you can allow metadata and data reads while withholding anything you would rather keep off. Scoping is applied per operation.

What authentication does the WTO Timeseries API use?

The API authenticates with a subscription key sent as the `subscription-key` query parameter. Jentic injects the key from your stored credential when a call runs, so it never appears in your agent's prompt.

How do I know which indicator and economy codes to use?

The API lists indicators, reporting and partner economies, product classifications, and time periods, so you can resolve valid codes before requesting the numeric data.

What does the data endpoint return?

The data endpoint returns the numeric trade statistics time series for a chosen indicator, economy, and product across the covered years, along with units and value flags.

How does an agent find WTO Timeseries operations in Jentic?

The agent searches Jentic by intent, such as retrieving export values between two economies, and Jentic returns the matching operations ready to run under your subscription key.

Apiportal Wto WTO Timeseries API

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey14 EndpointsREST

For Agents

Lets an AI agent query World Trade Organization trade statistics, first discovering the available indicators, economies, and products and then retrieving the numeric time series.

Use for: I need to find which trade indicators the WTO dataset offers, List the reporting economies available for trade statistics, Retrieve the export values between two economies over time, Look up the product classifications used in the dataset

Not supported: Serves World Trade Organization trade and tariff statistics only; it does not cover company-level data or non-trade indicators, so pair it with another dataset for those.

The WTO Timeseries API serves international trade and tariff statistics published by the World Trade Organization over a REST interface. It exposes the indicators, reporting and partner economies, product classifications, and time periods that describe the data, and it returns the numeric time series itself for a chosen indicator, economy, and product. Calls authenticate with a subscription key passed as a query parameter.

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

98%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

36%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

86%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the WTO Timeseries API to your agent

Capabilities

Start building with WTO Timeseries API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Apiportal Wto WTO Timeseries API

Jentic AI Readiness Score

WTO Timeseries 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