Quickstart
Make your first authenticated call and render a product in a few minutes.
TypeScript SDK
A type-safe client covering every service, with retries, pagination, and HMAC built in.
API Reference
Every endpoint, request, and response — generated from the OpenAPI spec.
Core Concepts
Keys, environments, isolation, edge caching, and how money flows.
What you can build
The API spans 24 services across ~117 operations, grouped by the job they do. A storefront typically touches a handful; everything is available when you need it.Catalog & Discovery
Products, variants, specifications, collections, categories, AI semantic search, and
hybrid recommendations (similar, also-bought, next-likely, trending, personalized, bundles).
Cart & Checkout
Persistent carts and wishlists, dynamic pricing, promotions, gift cards, shipping rates, and
idempotent order creation with automatic inventory and accounting side effects.
Payments
Multi-provider payment initiation and verification (Stripe, PayPal, and regional processors),
with sandbox test mode built in.
Customers & Auth
Customer profiles and RFM analytics, plus customer authentication via native sessions or your
own identity provider (bring-your-own-auth).
Returns & Support
Shopper-initiated returns and store credit, and real-time customer↔store messaging.
Content & Storefront Analytics
Shoppable blog posts and lookbooks, and first-party traffic / funnel / revenue analytics
captured without a third-party tracking script.
Marketplace
Aggregate many merchants behind one storefront, with a unified cart and a single payment that
splits to each merchant automatically.
B2B (Wholesale)
Sell to business buyers at negotiated or tiered prices, on terms — request for quote, quote,
purchase order, and invoice, with credit and payment on net terms.
Integrations
Outbound webhooks, catalog ingestion (push or scheduled feed pull), and “Log in with GC” for
third-party tools.
Global by default
Per-store currency, multi-currency catalogs, and geographic pricing — currency always read from
store info, never assumed.
Why teams choose Galactic Core
One coherent contract
A single auth model, one consistent error shape (
{ error: { code, message } }), cursor
pagination, and sparse field selection across every endpoint — not a decade of accreted,
inconsistent APIs.Commerce, not just storage
Orders create journal entries, reduce stock, redeem gift cards, and update customer metrics
automatically. You call one endpoint; the operational side effects are handled.
Edge-first performance
Reads are served from a multi-tier edge cache, so catalog and pricing calls return in tens of
milliseconds worldwide.
Dedicated isolation
Each deployment runs on its own isolated stack — your data is never co-mingled with another
tenant’s. See Core Concepts.
Built-in sandbox
Every endpoint has a test environment keyed by your API key — build and test against realistic
data without touching production.
Generate a storefront
The SDK is consumable by AI storefront generators, so a complete, commerce-wired storefront can
be produced from the API surface alone.
Two ways to integrate
TypeScript SDK (recommended)
npm install @tybrite-labs/sdk → a typed client with a method per endpoint, automatic
retries, cursor pagination helpers, idempotency, and HMAC signing. Ideal for web and Node.js apps.REST API
Call
https://api.tybritelabs.com directly from any language or runtime. Bearer-key auth,
JSON in/out, served from the edge.Authentication at a glance
Galactic Core uses two key types — a full overview is in Authentication:- Publishable keys (
tybrite_pk_*) — read-only, safe in the browser (catalog, search, cart writes). - Secret keys (
tybrite_sk_*) — full read/write, server-side only (orders, payments, customer data).
Need help designing your architecture? Reach the team at
[email protected].