What is the SDK package name?
The SDK is published as @ryxel-ai/findata on npm. Install it with pnpm add @ryxel-ai/findata @hey-api/client-fetch.
A fully typed client generated from our OpenAPI spec: every endpoint, parameter, and response checked at compile time.
The SDK is generated from the OpenAPI 3.1 spec that documents the API. Every endpoint, parameter, and response body is typed, and the types regenerate when the spec changes. The client can't silently fall behind the API.
Install @ryxel-ai/findata from npm, configure the client with your API key, and call typed functions. Autocomplete lists the real parameters; the compiler rejects the wrong ones.
Optional React Query helpers ship in the box for teams building internal tools on @tanstack/react-query. Keep the SDK server-side: API routes, backend proxies, and server components. Browser code would expose your key.
Query parameters and response bodies are typed from the OpenAPI spec, so autocomplete and the compiler catch mistakes before production does.
The SDK is built from the same spec that documents the API. When an endpoint changes, the types change with it.
Options factories for @tanstack/react-query ship in the box for server components, API routes, and internal tools.
Drop the client into a Next.js route, a backend proxy, or a worker. Your API key stays off public frontends.
# pnpm add @ryxel-ai/findata @hey-api/client-fetch
import { client } from "@ryxel-ai/findata/client";
import { getInsiderTransactions } from "@ryxel-ai/findata/sdk";
client.setConfig({
baseUrl: "https://ryxel.io/api",
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await getInsiderTransactions({
query: { ticker: "TSLA", limit: 50 },
});Call typed functions from Next.js routes, Express handlers, or workers. Bad parameters fail at compile time, not in production.
The options factories plug straight into useQuery, so dashboards and admin tools get caching and refetching for free.
A typed client in a cron script reads like pseudocode and fails loudly when a field changes.
Wrap SDK calls as agent tools with typed arguments, so an LLM can only ask for parameters that actually exist.
The SDK is published as @ryxel-ai/findata on npm. Install it with pnpm add @ryxel-ai/findata @hey-api/client-fetch.
No. Embedding your API key in public frontend code exposes it. Use the SDK server-side: API routes, a backend proxy, or React Server Components.
Yes. Import options factories from @ryxel-ai/findata/react-query and they plug straight into useQuery.
The SDK is generated from the same OpenAPI 3.1 spec that documents the API. When the spec changes, the client regenerates, so type errors surface at build time instead of runtime.
Tell us what you're building and which datasets you need — we'll set you up with an account, an API key, and access to the data.