For Agents
Map ISIN, CUSIP, SEDOL, or tickers to FIGI identifiers and search Bloomberg's open instrument identifier dataset across four endpoints.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenFIGI 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 OpenFIGI API.
Map external instrument identifiers (ISIN, CUSIP, SEDOL, ticker, etc.) to FIGI via POST /mapping with a list of jobs
List the allowed values for any mapping key (idType, exchCode, marketSecDes) through /mapping/values/{key}
Search the FIGI universe by free-text query via POST /search with optional filters
Run filtered queries by name, ticker, exchange, or security type via POST /filter
GET STARTED
Use for: Map an ISIN to a FIGI for a given exchange, List the valid exchange codes accepted by the mapping endpoint, Search for instruments matching a company name, Filter all common stocks listed on the LSE
Not supported: Does not handle market quotes, trade execution, or fundamental data — use for instrument identifier mapping and FIGI search only.
OpenFIGI is the free public API maintained by Bloomberg's Open Source Office that maps third-party financial instrument identifiers — ISIN, CUSIP, SEDOL, ticker symbols — to the Financial Instrument Global Identifier (FIGI). The API exposes mapping, search, and filter operations across the global universe of equities, bonds, derivatives, and other instruments. Used by buy-side firms, fintech apps, and academic researchers as an open alternative to commercial security-master services. An optional X-OPENFIGI-APIKEY header increases the rate limit.
Resolve global cross-references for an instrument with one mapping request per identifier
Build security-master enrichment pipelines that turn third-party identifiers into stable FIGIs
Patterns agents use OpenFIGI API for, with concrete tasks.
★ Portfolio Identifier Enrichment
Enrich a portfolio file containing ISINs or tickers with FIGI identifiers so downstream systems can join across data vendors. POST /mapping accepts up to 100 jobs per request (without API key) and returns the matching FIGI for each, including share class and composite FIGI. Replaces costly commercial cross-reference services for many use cases.
POST /mapping with a body listing {idType: 'ID_ISIN', idValue: 'US0378331005'} and return the figi from the response.
Instrument Discovery
Search the FIGI universe by company name or partial ticker via POST /search. Useful for fintech apps adding a security picker — the endpoint returns ranked matches with FIGI, name, exchange, and security type so users can disambiguate share classes and listings before placing orders or running analyses.
POST /search with body {query: 'Apple'} and return the top 10 results' name, ticker, and exchCode.
Reference Data Lookup
Build a reference-data service that calls /mapping/values/{key} to fetch the canonical list of acceptable values for parameters like exchCode, idType, or marketSecDes. Useful for client-side validation in trading or research apps so users only submit accepted values.
GET /mapping/values/exchCode and return the full list of accepted exchange codes.
Agent-Driven Security Master Updates
An AI agent maintaining a portfolio analytics dataset can use Jentic to discover the OpenFIGI mapping operation and submit identifier-resolution jobs in batch each time a new instrument appears. Jentic handles credential injection if the deployment uses an API key, so the agent's prompts stay free of secret material.
Through Jentic, find the operation for "map an instrument identifier to FIGI" and call /mapping with the new ISINs from the dataset.
4 endpoints — openfigi is the free public api maintained by bloomberg's open source office that maps third-party financial instrument identifiers — isin, cusip, sedol, ticker symbols — to the financial instrument global identifier (figi).
METHOD
PATH
DESCRIPTION
/mapping
Map external identifiers to FIGI in batch
/mapping/values/{key}
List allowed values for a mapping parameter
/search
Free-text search across the FIGI universe
/filter
Filter instruments by structured criteria
/mapping
Map external identifiers to FIGI in batch
/mapping/values/{key}
List allowed values for a mapping parameter
/search
Free-text search across the FIGI universe
/filter
Filter instruments by structured criteria
Three things that make agents converge on Jentic-routed access.
Credential isolation
OpenFIGI's optional X-OPENFIGI-APIKEY is stored encrypted in the Jentic vault (MAXsystem). Jentic injects it as a header at execution so the agent runs at the elevated rate limit without ever holding the raw key in its prompt or memory.
Intent-based discovery
Agents query Jentic with intents like "map ISIN to FIGI" or "search for an instrument" and receive the matching OpenFIGI operation and body schema, including job-array shape for batch mapping.
Time to first call
Direct OpenFIGI integration: half a day for the four endpoints, batch shape, and rate-limit handling. Through Jentic: under 30 minutes.
Alternatives and complements available in the Jentic catalogue.
Specific to using OpenFIGI API through Jentic.
What authentication does the OpenFIGI API use?
OpenFIGI accepts an optional X-OPENFIGI-APIKEY request header that raises rate limits. Calls without a key still work at the public tier. Jentic stores the API key encrypted in MAXsystem and applies the header at execution so the value never reaches the agent's prompt context.
Can I map multiple ISINs in one request with the OpenFIGI API?
Yes. POST /mapping accepts an array of mapping jobs in a single request — up to 10 per request without a key, and up to 100 per request with a key. Each job contains an idType and idValue plus optional filters like exchCode.
What are the rate limits for the OpenFIGI API?
Without a key, /mapping permits 25 requests per 6 seconds and up to 10 jobs per request. With a key, the cap rises to 25 per 6 seconds with 100 jobs per request, plus higher daily ceilings — published on openfigi.com. /search and /filter share their own per-key limits.
How do I search for an instrument with the OpenFIGI API through Jentic?
Use the Jentic search query "search for a financial instrument by name". Jentic returns POST /search with its body schema; the agent supplies the query string and any optional filters, and Jentic routes the call. Sign up at https://app.jentic.com/sign-up.
Is the OpenFIGI API free?
Yes. OpenFIGI is operated by Bloomberg as an open service and is free at every tier. An optional API key raises rate limits but does not introduce charges.
What identifier types can OpenFIGI accept on the mapping endpoint?
OpenFIGI accepts ID_ISIN, ID_CUSIP, ID_SEDOL, ID_BB, TICKER, COMPOSITE_ID_BB_GLOBAL, and others. Call /mapping/values/idType for the full live list rather than hard-coding it, since the supported set changes over time.