Does access scale by seat?
No. Access is per dataset, not per user. One API key can serve the whole team's notebooks, dashboards, and internal tools.
A terminal priced for trading floors can't sit on every desk. An API can. Every analyst queries the same normalized datasets, programmatically.
Today
One shared seat, a queue at busy hours, and CSVs emailed around the team. By Friday nobody knows which export is current.
With RyxelData
One API key for the team. Same endpoints, same schemas, refreshed after each filing. Notebooks and dashboards rerun themselves.
A terminal priced for trading floors can't sit on every desk. So teams ration: one shared seat, a queue at busy hours, and a lot of screenshots in slide decks.
The workaround is worse. Analysts export CSVs by hand, email them around, and within a week nobody knows which version is current.
When everyone pulls data differently, the team argues about whose numbers are right instead of what the numbers mean.
FORM 4
Buys, sells, and option exercises within minutes of EDGAR. Each row links back to the filing.
13F
Institutional holders and manager-level positions. The ownership slide stops being a screenshot from a shared seat.
SPLC
Walk the disclosed network before you write the risk section. Concentration shows up here first.
HTTP
Anything that speaks HTTP. JSON in, JSON out. The same query the associate ran last week still works.
RyxelData delivers insider transactions, 13F holdings, Form 144 proposed sales, fund holdings, supply chain relationships, and IPO data over one REST API. Python, a notebook, an internal dashboard: anything that speaks HTTP works.
Everyone queries the same endpoints with the same schemas. The data refreshes minutes after new filings land on EDGAR, so the my-numbers-versus-your-numbers conversation goes away.
Each record links back to the source filing on EDGAR. When a number matters, the primary source is one click away.
Every analyst has the same access at the same time. No seat licenses, no queue, no CSV drift.
The team's shared queries become shared infrastructure: saved endpoints, notebooks, and dashboards that rerun themselves.
Analyst time goes to the thesis. The data layer is solved.
A terminal priced for the trading floor cannot sit on every desk. An API can. RyxelData sits next to Excel, the notebook, and whatever you already use for quotes.
One key covers the team's notebooks and internal tools. You are not buying another seat every time someone joins.
Same endpoints, same schemas. The argument moves from whose export is right to what the numbers mean.
Records carry the EDGAR link. When a number matters in a meeting, the filing is one click away.
No. Access is per dataset, not per user. One API key can serve the whole team's notebooks, dashboards, and internal tools.
Anything that speaks HTTP: Python, R, notebooks, BI tools, or internal dashboards. Responses are JSON, documented by an OpenAPI 3.1 spec.
Insider transactions are parsed within minutes of each EDGAR filing, Form 144 updates daily, and 13F positions land within days of the quarterly deadline.
Yes. Records carry a link to the source filing on EDGAR, so every figure traces back to the primary document.
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.