Do we have to replace the PM's terminal?
No. Most teams keep the existing terminal on the PM desk and use RyxelData for ownership, insider, and proposed-sale data everywhere else.
The PM can keep the expensive terminal. The rest of the book still needs ownership, insider, and selling-intent data they can query without waiting for a seat.
Today
One terminal on the PM's desk. Associates wait their turn, then screenshot 13F holders and insider prints into a deck.
With RyxelData
The same 13F, Form 4, and Form 144 record on every analyst machine, over one API, next to the OMS and the prime tools you already pay for.
A $30,000 terminal cannot go on every desk. Most hedge funds already know this. The PM keeps Bloomberg. Everyone else shares a login or works from last quarter's export.
That split shows up in the work. The associate building a long/short book needs holder concentration, recent insider buying, and whether affiliates just filed a sale. Those facts live in EDGAR. They do not need a full quote stack to be useful.
Buying another seat so someone can look up 13F holders is the expensive way to solve a data problem.
13F
Who owns the name, how much, and how that changed last quarter. Issuer aggregates answer crowding without a full table scan.
FORM 4
Open-market buys and sells within minutes of the filing. Filter to officers. Ignore grants. See the position after the trade.
FORM 144
Affiliates file the notice with the sell order. You see intended supply days before the matching Form 4.
SPLC
If the short's largest customer just warned, or the long depends on one supplier, the relationship is already disclosed.
RyxelData is the ownership and insider layer. It is not an OMS, not an EMS, and not a replacement for the PM's terminal. It sits next to those tools.
Analysts query 13F positions, insider transactions, Form 144 notices, supply-chain relationships, and IPO terms over REST or the TypeScript SDK. Same schemas for the whole team.
The PM can stay on Bloomberg. The book still gets holder data, insider prints, and proposed sales without another five-figure seat.
Associates stop queueing for a login to answer who owns a name. The query is the same one the PM would have run.
Form 144 plus Form 4 gives you intent and follow-through on the same book. Most terminals flatten that into one insider widget.
Research time goes to the pair, the spread, and the risk. The filings are a solved feed.
The common pattern is Bloomberg for the PM and a data API for everyone who builds the book. RyxelData is the second half of that pattern.
We do not execute, allocate, or replace the prime. We feed ownership and insider data into the stack you already run.
Access is per dataset, not per chair. The intern and the PM can hit the same endpoint.
A notebook, a dashboard, or a production job. JSON either way.
No. Most teams keep the existing terminal on the PM desk and use RyxelData for ownership, insider, and proposed-sale data everywhere else.
No. RyxelData is a data API. It complements the execution stack and prime tools you already have.
13F holdings and aggregates, Form 4 insider transactions, Form 144 proposed sales, supply-chain relationships, and IPO deal terms. We do not sell quotes, options chains, or an order blotter.
13F is quarterly by regulation, due 45 days after quarter end, and we process filings within days of the deadline. Insider trades update within minutes of each Form 4. Form 144 updates daily.
Yes. Access is per dataset, not per seat. One API key can serve notebooks, internal tools, and production jobs across the firm.
Share your use case and the datasets you need — we'll set up access for your team and one API key that covers it all.