OpenFeature and OFREP.

Resolve Flags through OFREP and map OpenFeature track() to Metric Events.

@splitch/sdk/openfeature is an OpenFeature-shaped Provider that talks OFREP Core on the Evaluation Worker. Pass a Client Key or API Key. The Environment comes from the credential.

import { SplitchOfrepProvider } from "@splitch/sdk/openfeature";

const provider = new SplitchOfrepProvider({
  baseUrl: "https://edge.splitch.dev",
  credential: "pk_...",
});

const details = await provider.resolveBooleanEvaluation("new-checkout", false, {
  targetingKey: user.id,
});

Each typed resolve POSTs /ofrep/v1/evaluate/flags/{key} and records Exposure when the Flag is under a live Experiment Run. That request consumes one Evaluation (ADR-0033).

track(eventName, context, details) submits a Metric Event to /api/sdk/events. It needs context.targetingKey. Metric Events consume zero Evaluations.

Bulk prefetch and Exposure

OFREP bulk evaluation (POST /ofrep/v1/evaluate/flags) resolves every Flag for one Evaluation Context and bills N Evaluations for N Flags. It does not record Exposure. A fresh live-Run assignment includes metadata.exposureTicket. Exposure happens when that ticket is redeemed on first local read, the same rule as evaluateAll. Cached local reads consume zero Evaluations.

Every SDK topic

Install: Add @splitch/sdk, read the export surface, and get one Flag resolving.
Credentials: Client Key evaluates, API Key peeks. Pass exactly one.
The six methods: Which calls fire an Exposure, and which credential each needs.
evaluateAll and bootstrap: Resolve every Flag once, then hydrate a browser client without another fetch.
idempotencyKey: The SDK generates a key per call. Supply one when your application manages retries.
Failure behavior: Server evaluation never throws on a platform failure and never hides one. Empty or non-string explicit idempotency keys throw, as does UUID generation when the runtime cannot provide it. Peek throws, and so does a browser read before init().
Exposure dedup: Repeat evaluations replay locally. Run boundaries do not.
Options: endpoint, timeoutMs, retries, logger, transport, onResolution.
Node.js: Evaluate on the request path from a Node server, with one client for the process.
Browser client: Fetch once, read Flags synchronously, and fire Exposures on first use.
React bindings: Provide one initialized browser client and subscribe each hook to one Flag.
Convex: Local Flag evaluation inside Queries and Mutations, with transactional Exposures.
Cloudflare Workers: Deploy an integration Worker into your own account and evaluate over a service binding.
Sentry: Feed both halves of Sentry's suspect-flag detection: change tracking and evaluations.
OpenFeature and OFREP: Resolve Flags through OFREP and map OpenFeature track() to Metric Events.