Get started

GLEIF API for AI agents

GLEIF is the public registry behind Legal Entity Identifiers, giving free access to corporate ownership and identifier records. Compliance and finance teams use it to verify legal entities. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect GLEIF APISee the 21 actions ↓
AnalyticsNo authMCP + RESTgleif.org
AUDIT LOG · GLEIF APIPOLICY: acme-support
09:41:07 · claude · u_8f2read
gleif_api.list_lei_isins
List LEI ISINs✓ allowed · 212ms
09:41:08 · claude · u_8f2read
gleif_api.get_lei_record
Get LEI Record✓ allowed · 164ms
EVERY GLEIF API CALL, ON THE RECORD
01 · USE CASES

What agents do in GLEIF API.

01

Look up a company's LEI record

Search for a counterparty's Legal Entity Identifier record to confirm its registered legal name.

02

Check an entity's parent company

Pull the parent relationship for an entity to understand its ownership structure before onboarding.

03

Search records by entity name

Search LEI records by fuzzy name match when the exact identifier for a business is not known.

02 · ACTIONS

21 GLEIF API actions, graded by risk.

Every GLEIF API action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

21

Look things up. Allowed by default.

  • gleif_api.get_lei_record
    Get LEI Record
  • gleif_api.list_lei_isins
    List LEI ISINs
  • gleif_api.get_reference_item
    Get Reference Item
  • gleif_api.search_lei_records
    Search LEI Records
  • gleif_api.get_autocompletions
    Get Autocompletions
  • gleif_api.list_child_entities
    List Child Entities
  • gleif_api.list_reference_data
    List Reference Data
  • gleif_api.get_successor_entity
    Get Successor Entity (Deprecated)
  • gleif_api.get_fuzzy_completions
    Get Fuzzy Completions
  • gleif_api.get_parent_information
    Get Parent Information
  • gleif_api.get_related_lei_record
    Get Related LEI Record
  • gleif_api.list_successor_entities
    List Successor Entities
  • gleif_api.list_child_relationships
    List Child Relationships
  • gleif_api.list_registration_agents
    List Registration Agents
  • gleif_api.get_lei_issuer_for_record
    Get LEI Issuer for Record
  • gleif_api.list_fund_or_branch_entities
    List Fund or Branch Entities
+ 5 MORE

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

GLEIF API in three steps.

  1. 01Your users connect GLEIF APIThey add their GLEIF API no auth on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls GLEIF API through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('gleif_api', {
  read: 'allow',
  write: 'ask',        
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How GLEIF API connects.

GLEIF API needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.

The same GLEIF API connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
No auth
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use GLEIF API from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More analytics apps.

Gong58 actionsSerpApi59 actionsPeople Data Labs27 actionsPostHog507 actions21risk8 actionsAkta19 actionsAlpha Vantage56 actionsAmplitude54 actions
ALL ANALYTICS APPS →
07 · FAQ

GLEIF API and Arc0, answered.

Q01

Can I use GLEIF API with Claude, ChatGPT or Cursor?

Yes. Connect GLEIF API to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the GLEIF API actions you allow.

Q02

How do users connect GLEIF API?

GLEIF API needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.

Q03

Which GLEIF API actions can my agent take?

21 in total: 21 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in GLEIF API?

Yes. Allow read actions and deny writes in the GLEIF API policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call GLEIF API too?

Yes. The same GLEIF API connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug GLEIF API into your agent.

Your users connect GLEIF API once, under your brand. Your agent gets 21 actions behind your policies, with every call on the record.

Connect GLEIF APIBrowse all apps →

Free to build · MCP + REST · Audit log on every plan