Brokerage & trading apps

Fisk can supply the company research around your existing instrument and trading experience. In the initial pilot, connect a designated Fisk Pro account through your backend using the same OAuth flow and shared limits as MCP. Agree permitted data use with Fisk before serving it to customers.

A company research page

Build a page in three layers:

Layer	Fisk data	User experience
Company identity	Company profile	Name, exchange, issuer link and available logo
Reported performance	Financial facts	A period-aware chart or metric table with source links
Evidence and timing	Documents and events	Reports, relevant pages and upcoming announcements

Start from an explicit mapping between your instrument ID and the Fisk company ID. Keep exchange and entity identity alongside the mapping.

A source-linked financial card

A compact metric card should answer four questions:

1. What is the measure and reporting period?
2. Which currency and entity scope does it use?
3. Is it restated, unavailable or otherwise qualified?
4. Where can the user read the original source?

For example, a net income card can link directly to the link and page_number returned with its fact. A source drawer can then call the document-page endpoint when the user opens it, instead of fetching excerpts for every card.

An event view

Load an event interval appropriate to the screen. A one-month calendar does not need a full year of data.

Use separate visual states for confirmed dates, estimated windows and events awaiting announcement. Preserve the source URL and timezone where available.

A document search

Require a company selection before a keyword search. Submit when the user confirms the query, and show results with a title, page and source link.

Avoid search-as-you-type calls to the document endpoint. The pilot applies a minimum search interval and shares the search allowance with the account’s use of Fisk Web.

Keep credentials on your backend

Your app
   │ authenticated customer request
   ▼
Your backend
   │ designated Pro account's OAuth access token
   ▼
Fisk API
   │ sourced data + periods + units + quota metadata
   ▼
Your backend → your research UI

Authorize the customer before serving data. Keep provider credentials outside browser bundles and mobile binaries. Handle revoked access and quotas centrally.

Capacity planning

Share your expected active users, screens per session and update cadence with Fisk. Business integrations initially have the same 100 data calls per day and 6 per minute per Pro account, shared across API and MCP. Connecting more clients does not increase that allowance.

Load data when the user needs it, deduplicate simultaneous requests and avoid unbounded fan-out across companies. Agree any caching, retention and redistribution policy with Fisk. Discuss greater capacity before planning a launch that exceeds the pilot limits.

Trading data boundaries

Use your execution provider for order entry, balances and executable market prices. Fisk’s available quotes may be delayed or historical and must retain their source and trading date.

These endpoints are designed for research context. They do not provide trade execution, personalized recommendations or portfolio management.