OpenClaw · Pay per call · No feed required

Financial instrument data
with OpenClaw Agent.

Drop Financial Instrument Data into your OpenClaw agent as a single tool call. Pass any identifier — ISIN, CUSIP, FIGI, or ticker — and get back the complete security-master record: every cross-mapped identifier, asset-class and sector classifications, and corporate-actions history. Billed per resolved result. No feed to license, no batch file to load, no long-lived credentials to manage.

  • Single OpenClaw tool — one POST
  • Budget caps honored per run
  • No feed license required
AI agent
OpenClaw
Instrument Data
Financial Instrument API
Identifiers supported 4 types ISIN, CUSIP, FIGI, and ticker accepted as input. Your OpenClaw agent passes any one and gets back the full cross-mapped set.
Instruments covered 50M+ Equities, fixed income, ETFs, funds, and derivatives across global exchanges and OTC markets — resolved on demand when your agent calls.
Time to wire it in ~5 min Register one tool in OpenClaw, paste the endpoint, ship. No vendor onboarding required.
What OpenClaw builders ship

Real OpenClaw agents that rely on this tool.

Each pattern below is a single OpenClaw agent with Financial Instrument Data registered as one tool. The agent only spends when it resolves a result.

OpenClaw reconciliation agent

Resolve every identifier mismatch in a counterparty file.

An OpenClaw reconciliation agent processes an incoming counterparty file, calls Financial Instrument Data for each unmatched position identifier, and writes the resolved cross-map back to the record — all in a single agent run. Counterparty ISINs resolve to internal CUSIPs, FIGI references resolve to tickers, and the file is clean before the next workflow step.

Counterparty file row: ISIN GB0002634946 → resolve to CUSIP, FIGI, primary ticker, and exchange code → write to reconciliation record
OpenClaw instrument onboarding agent

Enrich any unknown security the moment it arrives.

An OpenClaw OMS or PMS agent triggers when an unknown instrument hits the system, calls the tool to return the full identifier set, asset-class classification, and sector tags, and writes the enriched record before the instrument enters any routing or display logic. No overnight batch job, no manual lookup, no overnight wait.

Unknown instrument: FIGI BBG000B9XRY4 → return full identifier set, asset class, sector classification, exchange details → write to security master
OpenClaw corporate-actions agent

Check any holding for pending events at the point of decision.

An OpenClaw portfolio or operations agent triggers at decision time — before a trade, before a report, before a client display update — and calls Financial Instrument Data to pull the corporate-actions record for each relevant holding. Pending splits, mergers, dividends, and name changes surface before they can affect a downstream calculation.

Holdings review: CUSIP 037833100 → return pending and historical corporate actions → flag any events affecting today's NAV calculation
OpenClaw compliance and routing agent

Validate and classify any instrument on the fly.

An OpenClaw compliance or order-routing agent calls the tool to confirm that an identifier is real and currently active, then tags the instrument with asset class and regulatory classification before the order proceeds. One tool call replaces a lookup against a standing classification subscription and a separate validation step.

Order validation: ticker AAPL exchange XNAS → confirm identifier is active, return asset class, sector, and regulatory classification → clear for routing
OpenClaw-ready in two minutes

Complete security record out, inside every OpenClaw agent.

Register one tool and your OpenClaw agent resolves any instrument identifier to a complete security-master record on demand. Idle runs cost zero. That's the entire deal.

  • Single OpenClaw tool
  • Budget caps honored
FAQ

OpenClaw-specific questions.

If something below doesn't cover your case, ping us — we work directly with OpenClaw builders, no sales process.

How does this register as an OpenClaw tool?

+

It's a single POST endpoint with a typed body. You register it in OpenClaw the same way you'd register any HTTP tool — endpoint, schema, price-per-call. OpenClaw uses the price to enforce budget caps and to show what each instrument resolution will cost before the agent runs.

Does OpenClaw need a long-lived login to call the tool?

+

No. The tool is billed per call with no long-lived credentials to manage, leak in agent logs, or rotate.

Can an OpenClaw agent resolve a batch of instruments in a single run?

+

Yes. An OpenClaw agent can iterate over a list of identifiers, call the tool per instrument, accumulate resolved records, and pass the enriched batch downstream — all within a single agent run and a single budget cap.

What happens when an OpenClaw run hits its budget cap mid-batch?

+

The API returns resolved records for instruments matched so far and stops. OpenClaw treats this as a normal tool result so the agent can decide whether to request more budget, process the partial batch, or queue the remainder for a follow-up run.

Can OpenClaw call this tool in real time, not just in scheduled batch runs?

+

Yes. The tool responds in under a second, so an OpenClaw agent triggered by a trade event, an incoming message, or an OMS webhook can resolve an identifier in real time — one call per instrument, billed per resolved result.

How is this different from giving OpenClaw access to a full reference-data feed?

+

A feed subscription doesn't fit OpenClaw's tool model — the tool can't report a true per-call cost, so OpenClaw can't do real budget planning against it. Financial Instrument Data reports an honest per-call cost up front, which is what OpenClaw was designed to consume.