data-figi

Resolve ISIN, CUSIP, SEDOL, and tickers to FIGI and normalized instrument metadata.

7|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fall-development-rob/corp_finance --skill data-figi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-figi
Source: https://github.com/fall-development-rob/corp_finance/tree/main/.claude/skills/data-figi
Command: npx skills add https://github.com/fall-development-rob/corp_finance --skill data-figi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves and normalises disparate financial instrument identifiers by mapping ISINs, CUSIPs, SEDOLs, and tickers to FIGI and unified instrument metadata so datasets from multiple sources can be reliably joined and analysed.

Core Features & Use Cases

  • Identifier Mapping: Map single identifiers or batches to FIGI, ticker, exchange, currency, security type, and instrument name.
  • Search & Discovery: Find FIGIs by keyword or partial ticker and filter results by exchange code, MIC, currency, security type, or market sector.
  • Use Case: Convert an ISIN column in a fixed income dataset to FIGI and ticker columns to join with pricing and fundamentals from other vendors.

Quick Start

Map a list of ISINs and CUSIPs to their FIGIs and tickers, returning exchange, currency, and security type.

Frequently Asked Questions about data-figi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map ISIN and CUSIP identifiers to FIGI for data normalization?

To map ISIN and CUSIP identifiers to FIGI, you resolve single or batch identifiers to FIGI and normalized instrument metadata, returning ticker, exchange, currency, and security type for reliable multi-source dataset joins.

Can I convert a list of SEDOLs and tickers to FIGI in bulk?

Yes, you can convert SEDOLs and tickers to FIGI in bulk. The identifier mapping process supports batch inputs, resolving multiple financial instrument identifiers to FIGI and unified metadata simultaneously.

What is the best way to join fixed income datasets using different vendor identifiers?

The best way to join fixed income datasets is mapping ISIN columns to FIGI and ticker columns, creating a normalized identifier layer to reliably match pricing and fundamentals from different vendors.

Does identifier mapping to FIGI support filtering by exchange code and currency?

Yes, identifier mapping to FIGI supports attribute filtering. You can filter resolved financial instruments by exchange code, MIC, currency, security type, or market sector during the search and discovery process.

Do I need an OPENFIGI_API_KEY to resolve financial instrument identifiers?

You do not need an OPENFIGI_API_KEY to resolve financial instrument identifiers, but providing an optional key increases your rate limits when mapping ISINs, CUSIPs, and SEDOLs to FIGI.

Why does multi-source reconciliation require mapping to FIGI?

Multi-source reconciliation requires mapping to FIGI because disparate datasets using different tickers and identifiers need a unified instrument metadata layer to accurately join and analyze financial data across vendors.