Can I buy one dataset instead of a bundle?
Yes. Access is per dataset, so you pay for the feed your feature needs and add more when the product calls for them.
Ship the data feature your roadmap keeps deferring. A typed SDK, an OpenAPI spec, and per-dataset access: buy what you need, when you need it.
Today
Users asked for insider activity, an IPO calendar, or fund look-through. Procurement wants a catalog contract. The sample responses in the vendor PDF do not match production.
With RyxelData
One dataset, one key, a typed SDK generated from the same spec as the docs. Prove the feature this sprint. Add datasets when the product does.
Your users asked for insider activity on the stock page, or an IPO calendar, or fund look-through. The feature is well understood. The data isn't.
Legacy vendors sell the catalog: a large annual contract for a bundle of datasets, when you need one feed to validate one feature. Procurement alone can kill a quarter.
Then the integration itself is a tax: bespoke auth, sample responses that don't match production, and field documentation that lives in a PDF.
SDK
Install @ryxel-ai/findata. Autocomplete lists the real parameters. The compiler rejects the wrong ones.
FUNDS
N-PORT portfolios, up to 10,000 positions per fund. The overlap view your users keep asking for.
IPO
Offer terms, underwriters, lockups, last-year financials. Drop them into a list, not a prospectus parser.
AUTH
Authorization header, JSON out, X-RateLimit headers on every response. Keep the key off the browser.
RyxelData sells access per dataset. Start with insider transactions or IPO data, prove the feature, and add datasets when the roadmap does.
The TypeScript SDK is generated from the same OpenAPI 3.1 spec that documents the API. Autocomplete works, the compiler catches bad parameters, and the docs show real sample responses.
One API key covers every dataset on your account. Auth is a Bearer header, responses are JSON, and rate limits are printed on every response in X-RateLimit headers.
The feature ships this sprint instead of next quarter. The data layer is an API call, not a vendor negotiation.
Your key stays server-side. The SDK drops into API routes, a backend proxy, or server components, so nothing sensitive reaches the browser.
When the product grows, the data grows with it. Add a dataset to the account and the same key, client, and patterns keep working.
The data feature is rarely the whole product. RyxelData sits behind your API routes and your UI. It does not try to be your app.
Start with the feed the ticket asks for. Add the next one when the roadmap does, on the same key and client.
SDK and REST belong in API routes, proxies, and server components. A key in the browser is a leaked key.
Sample responses come from the same OpenAPI spec that generates the SDK. What you read is what you ship.
Yes. Access is per dataset, so you pay for the feed your feature needs and add more when the product calls for them.
Yes. @ryxel-ai/findata is a TypeScript client generated from the OpenAPI 3.1 spec, with optional React Query helpers.
No. A key in browser code is visible to anyone who opens dev tools. Call the API from your backend, API routes, or server components.
Contact us at [email protected] with the datasets you need. We set up the account and the API key with you.
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.