KosmoKrator

data

OpenFIGI CLI for AI Agents

Use the OpenFIGI CLI from KosmoKrator to call OpenFIGI tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

OpenFIGI CLI Setup

OpenFIGI can be configured headlessly with `kosmokrator integrations:configure openfigi`.

Install, configure, and verify
# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure openfigi --enable --read allow --write ask --json
kosmokrator integrations:doctor openfigi --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

KeyEnv varTypeRequiredLabel
api_key OPENFIGI_API_KEY Secret secret no API Key

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call
kosmo integrations:call openfigi.openfigi_mapping '{}' --json
Provider shortcut
kosmo integrations:openfigi openfigi_mapping '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands
kosmo integrations:docs openfigi --json
kosmo integrations:docs openfigi.openfigi_mapping --json
kosmo integrations:schema openfigi.openfigi_mapping --json
kosmo integrations:search "OpenFIGI" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

openfigi.openfigi_mapping

Map third-party identifiers to FIGIs.

Read read
Parameters
none
Generic call
kosmo integrations:call openfigi.openfigi_mapping '{}' --json
Shortcut
kosmo integrations:openfigi openfigi_mapping '{}' --json

openfigi.openfigi_mapping_values

List supported values for OpenFIGI mapping job properties.

Read read
Parameters
none
Generic call
kosmo integrations:call openfigi.openfigi_mapping_values '{}' --json
Shortcut
kosmo integrations:openfigi openfigi_mapping_values '{}' --json

openfigi.openfigi_search

Search for FIGIs using keywords and optional filters.

Read read
Parameters
none
Generic call
kosmo integrations:call openfigi.openfigi_search '{}' --json
Shortcut
kosmo integrations:openfigi openfigi_search '{}' --json

openfigi.openfigi_filter

Filter for FIGIs using OpenFIGI instrument filters.

Read read
Parameters
none
Generic call
kosmo integrations:call openfigi.openfigi_filter '{}' --json
Shortcut
kosmo integrations:openfigi openfigi_filter '{}' --json

openfigi.openfigi_schema

Retrieve the current OpenFIGI OpenAPI schema.

Read read
Parameters
none
Generic call
kosmo integrations:call openfigi.openfigi_schema '{}' --json
Shortcut
kosmo integrations:openfigi openfigi_schema '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

openfigi.openfigi_mapping 0 parameters
Schema command
kosmo integrations:schema openfigi.openfigi_mapping --json
ParameterTypeRequiredDescription
No parameters.
openfigi.openfigi_mapping_values 0 parameters
Schema command
kosmo integrations:schema openfigi.openfigi_mapping_values --json
ParameterTypeRequiredDescription
No parameters.
openfigi.openfigi_filter 0 parameters
Schema command
kosmo integrations:schema openfigi.openfigi_filter --json
ParameterTypeRequiredDescription
No parameters.
openfigi.openfigi_schema 0 parameters
Schema command
kosmo integrations:schema openfigi.openfigi_schema --json
ParameterTypeRequiredDescription
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.