Skip to content

Governed OpenBB financial-data provider

OpenBB Open Data Platform (ODP) is deployed as an isolated external service for normalized financial data. It is not an AncientOS authority, agent, reasoning layer, transport, or user-facing standalone application.

Ownership boundary

The request path is:

transport -> canonical Luna ingress -> financial intent -> Rubick capability
-> Lich read-only policy -> AncientOS OpenBB adapter -> OpenBB REST service
-> TMX or Yahoo Finance -> Zeus evidence -> capability cognition -> renderer

Rubick owns capability identity and provider relationships. Lich owns authority. The OpenBB adapter owns the allowlisted network boundary and compact AncientOS result projection. OpenBB and its selected provider supply normalized external data. Zeus-style evidence records provenance. Cognition explains semantics but contains no current values or provider availability. Oracle/Luna presents the observation without gaining brokerage, trading, network, or mutation authority.

Raw OpenBB REST URLs and its MCP tool universe are not exposed to the model. OpenBB MCP remains a possible future interoperability option subject to the existing AncientOS MCP discovery, authorization, and evidence boundaries.

Deployment

Compose service openbb is internal to llm-net and exposes port 6900 only to other Compose services. It has no host port binding. Its local readiness check queries /openapi.json; external provider success is evaluated separately for each request.

The image uses the OpenBB 4.7.2-compatible package set:

  • openbb-core==1.6.13
  • openbb-equity==1.6.2
  • openbb-etf==1.6.2
  • openbb-platform-api==1.3.6
  • openbb-tmx==1.5.2
  • openbb-yfinance==1.6.3

TMX and Yahoo Finance currently require no provider credentials. Future credentialed providers must use the existing secret/environment conventions; credentials must never enter evidence, cognition, prompts, or logs.

Canonical capability slice

  • inspect_openbb_readiness
  • inspect_equity_quote
  • inspect_equity_price_history
  • inspect_equity_profile
  • inspect_equity_fundamentals
  • inspect_equity_metrics
  • inspect_etf_information

All are read-only external-provider observations with no trading or mutation authority. Equity/ETF research remains separate from Prophet prediction-market intelligence and its disabled execution boundary.

Broad conversational equity-status questions resolve to a bounded composition of inspect_equity_quote followed by inspect_equity_price_history. This means “current picture” or “how is this equity doing?” currently describes the latest provider-reported quote plus the default bounded recent price-history window. Specific quote, history, profile, fundamental, metrics/comparison, and ETF requests retain precedence and invoke only their narrower capability paths.

The deterministic renderer calculates start-to-end close movement from the canonical history rows. It labels the quote as latest available/provider-reported rather than real-time unless provider evidence establishes real-time semantics. The initial composition does not include governed financial news, event, social sentiment, or causal-explanation evidence; those remain a possible future capability extension rather than being inferred from price movement.

Provider choice is deterministic and visible. The initial adapter uses TMX for known Canadian quote, history, profile, and ETF requests, and Yahoo Finance for fundamentals/metrics where TMX does not expose the selected endpoint. An explicit internal provider override is preserved in evidence. Provider-specific symbol mapping is local to the adapter; it is not a global symbology service. There is no silent provider fallback.

Boundedness and evidence

History defaults to 30 days, cannot exceed 93 calendar days, and includes at most 31 daily rows in Luna context. Annual fundamentals include at most two periods. Comparisons accept at most four explicitly identified symbols. Descriptions are truncated to 600 characters, and all endpoint projections use small allowlists of fields.

Successful evidence records the AncientOS capability, OpenBB service and version, endpoint, underlying provider, requested and provider symbols, bounded parameters, provider timestamp, query timestamp, compact result, warnings, and evidence hash. Provider support, installation, configuration, endpoint availability, and query success remain distinct states.

Failures distinguish service unavailability, timeout, endpoint absence, provider installation or credential problems, rate limiting, symbol absence, empty results, provider request failure, and malformed responses. Failed reads do not produce inferred financial values.

Cognition

financial_market_data_semantics covers price, historical-period, exchange, currency, provider attribution, and missing-data semantics. equity_fundamental_semantics adds reporting-period, valuation, profitability, growth, leverage, and dividend interpretation. Both are inert request-scoped context and grant no authority.

Licensing boundary

OpenBB ODP is licensed separately from AncientOS. OpenBB currently describes ODP as AGPL-licensed with a commercial-license option. AncientOS communicates with it as a separate network service, but OpenBB and underlying provider licensing and terms remain independently applicable. This note does not determine legal obligations or provide legal advice. Maintainers must review current OpenBB and provider terms when deploying or redistributing the integration.

References: