Agent-native safety, declared in the contract.

Read-only financial data

All market, company, news, macroeconomic, and congressional-disclosure tools are read-only and non-destructive. They do not place trades, route orders, move funds, or modify an upstream financial record.

Three workflow tools are intentionally not marked read-only: product feedback, catalog-access requests, and human-reviewed upgrade requests. Their descriptions explain the saved action, and none is destructive.

Authorization and payment boundaries

Anonymous catalog discovery and the bounded Free allowance require no API key. When an MCP host needs identity or paid access, Unquant uses OAuth Authorization Code with PKCE. The host owns its credentials and should store them in its secure credential facility.

An agent must explain the recurring price, ask permission, and wait for a clear yes before opening a payment confirmation flow. Stripe remains the billing source of truth; tool output cannot silently authorize a charge.

Bounded inputs and outputs

Public tools use explicit input and output schemas. Data responses are normalized, row-bounded, and paginated. Raw upstream payloads and source-specific fields are not part of the public interface. Returned article titles and summaries are treated as untrusted data rather than executable instructions.

Privacy and telemetry

Browser analytics are cookieless, use a random page-lifetime identifier, and stop when Global Privacy Control or Do Not Track is enabled. Agent and crawler telemetry is designed around request metadata and privacy-safe identifiers rather than query contents. See the Privacy Policy for the current public terms.