@ryu/core-client

The platform-agnostic, typed client for a Ryu Core node. Part of Ryu.

@ryu/core-client is the shared HTTP client every surface uses to talk to a Ryu Core (and Gateway) node. It has no platform dependencies (no localStorage, no Tauri, no React), so the desktop (Tauri webview) and mobile (React Native / Expo) share the same domain modules verbatim. The base URL and bearer token always come from the caller's active node ({ url, token }), never hardcoded: Core listens on :7980 but the active node may be remote.

Tier: Closed, proprietary (A Major Pte. Ltd.)

What it provides

• HTTP primitives (client.ts, root export): ApiTarget, request, apiUrl, makeHeaders, plus the marketplace buyer-token seam (BUYER_TOKEN_HEADER, setBuyerTokenProvider, buyerTokenHeader). Bearer auth and base-URL handling live here in exactly one place.
• Typed domain modules (subpath exports): one file per Core feature: agents, chat, models, engines, spaces, skills, tools, workflows, teams, monitors, meetings, schedules, voice, mesh, mcp, plugins, recipes, delegation, goals, sessions, runs, and more.
• Subpath imports: pull a feature by path: import { fetchAgents } from "@ryu/core-client/agents". The root re-exports only the HTTP primitives by design (no kitchen-sink barrel).

Role

Designed to be shared verbatim by the desktop and mobile surfaces. Surface-specific concerns (the desktop buyer-token / presence headers, the mobile secure-store token) are layered on top by each app, not here. Consumed today by apps/native.

License

Proprietary. See LICENSE. © 2026 A Major Pte. Ltd.