Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GlobalWineScore API Documentation, 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%2Fglobalwinescore.com%2Fglobalwinescore" | shStep 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%2Fglobalwinescore.com%2Fglobalwinescore" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with GlobalWineScore API Documentation API.
Retrieve the latest GlobalWineScore for every wine in the catalogue in one call
Pull the historical score timeline for a wine to chart how its rating has evolved
Sort scores by date or score (ascending or descending) to surface the highest-rated or newest entries
Sync a local product database to the API by polling /globalwinescores/?ordering=-date and ingesting only the newest records
GET STARTED
Switch between JSON and XML response formats via the Accept header or format query parameter
Patterns agents use GlobalWineScore API Documentation API for, with concrete tasks.
★ Wine Retailer Catalogue Enrichment
Online wine retailers can enrich product pages with a critic-aggregated score by mapping their SKUs to GlobalWineScore wines and reading /globalwinescores/latest/ on a daily schedule. Showing a normalised score next to each bottle lifts conversion versus listing several critic scores side by side. Integration is a few hours given the small surface area.
GET /globalwinescores/latest/ with ordering=-score, paginate, and write each wine's score onto the matching SKU in the retailer's catalogue.
Investment-Grade Wine Trend Analysis
Wine investment platforms and merchants tracking secondary-market value can pull historical scores via /globalwinescores/?ordering=-date to chart how a vintage's rating has moved over time, then correlate against auction prices. The API returns JSON or XML so it slots into existing analytical pipelines with minimal transformation.
GET /globalwinescores/?ordering=-date and filter the response to a single wine ID, then build a time series of date-versus-score values.
AI Sommelier Recommendations
An AI sommelier agent can use GlobalWineScore through Jentic to back its recommendations with a critic-aggregated score, returning answers like "this 2016 vintage scored 94 on GlobalWineScore - higher than the 2015 you tried." Because the API is two endpoints, the agent only needs one Jentic search to integrate the data source.
Search Jentic for 'latest wine scores', load the schema for GET /globalwinescores/latest/, and execute it with a wine name filter, then summarise the top result.
2 endpoints — globalwinescore aggregates wine ratings from major critics into a single normalised score per wine and vintage, then exposes the catalogue through a small restful api.
METHOD
PATH
DESCRIPTION
/globalwinescores/latest/
List the latest GlobalWineScore for every wine
/globalwinescores/
List all historical GlobalWineScore entries
/globalwinescores/latest/
List the latest GlobalWineScore for every wine
/globalwinescores/
List all historical GlobalWineScore entries
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GlobalWineScore API by hand means learning its Authorization token header auth and remembering which of its two lookup endpoints takes which query parameters. Through Jentic you install once, import the GlobalWineScore API from the API Directory, store the token once, and your agent calls it.
Permission scoping
GlobalWineScore takes its filters as query parameters rather than resource ids in the path, and both endpoints are read-only, so scope the agent to the operations it needs, such as fetching the latest scores or historical ratings. You choose that operation set, so it reads score data without any write ability.
Credential isolation
Your GlobalWineScore token 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 'latest wine scores' or 'historical wine rating', and Jentic returns the matching GlobalWineScore endpoint with its query parameter schema so the agent does not need to remember the latest versus full-history split.
Alternatives and complements available in the Jentic catalogue.
Specific to using GlobalWineScore API Documentation API through Jentic.
What authentication does the GlobalWineScore API use?
GlobalWineScore uses token authentication. Send Authorization: Token {YOUR-API-TOKEN} on each request over HTTPS. The keyword Token is required by the API. Tokens are issued from the My account > API page after applying through globalwinescore.com/api/. Through Jentic the token is held in the vault.
What are the rate limits for the GlobalWineScore API?
The published limit is 10 requests per minute. Catalogue-sync jobs should poll /globalwinescores/?ordering=-date and ingest only newer records rather than crawling the full catalogue on every run, as recommended in the official documentation.
Can I get the historical score timeline for a wine?
Yes. GET /globalwinescores/ returns historical scores and supports ordering by date or score. Filter the response client-side by wine ID to build a per-wine time series.
How do I sync my retailer catalogue through Jentic?
Search Jentic for 'latest wine scores', load the schema for GET /globalwinescores/latest/, and execute it. Page through results and upsert into your product table. Run pip install jentic to get started.
Does the API support XML output?
Yes. The API supports JSON (default) and XML. Send Accept: application/xml or pass format=xml as a query parameter to receive the response in XML for legacy importers.
Is the GlobalWineScore API free?
GlobalWineScore offers tiered usage plans rather than a free public tier; details are at globalwinescore.com/plans. Apply for a token via the API page to see the plan attached to your account.
Can I limit what my agent is allowed to do with the GlobalWineScore API?
Yes. Because you run Jentic One yourself, your own rules decide which GlobalWineScore operations and credentials the agent may use. Both endpoints are read-only, so you can scope the agent to just the calls it needs, such as fetching the latest scores or reading the historical rating timeline, and its filters are passed as query parameters rather than path resource ids. That means the agent reads score data within the operation set you choose and has no ability to write.
Know of an official OpenAPI document? Contribute it →
For Agents
Look up consolidated wine scores and historical rating trends from GlobalWineScore, the aggregator of major critic ratings.
Use for: I need to get the latest score for every wine in GlobalWineScore, Find the historical scores for a specific Bordeaux vintage, Get the top-rated wines by GlobalWineScore, List the most recently scored wines
Not supported: Does not handle wine inventory, e-commerce orders, or auction prices - use for aggregated critic wine score lookup and historical rating trends only.
GlobalWineScore aggregates wine ratings from major critics into a single normalised score per wine and vintage, then exposes the catalogue through a small RESTful API. Two endpoints cover the main use cases: pulling the latest GlobalWineScore for every wine, and reading the full historical score timeline for trend analysis or back-testing. Token-based authentication and a published rate limit of 10 requests per minute make it suitable for catalogue-sync jobs rather than per-page lookups.