For Developers

Build once. Connect everywhere SageHenny operates.

SageHenny is being designed as a shared developer platform for authenticated packages, APIs, SDKs, webhooks, sandbox environments, entitlements, themes, agents, and release governance.

Read API docs Manage applications

Platform layers

Infrastructure still earning its way into production.

These capabilities are planned. Availability is not claimed beyond what exists today.

Reusable SageHenny-owned technology distributed as authenticated packages instead of copied into every product.

@sagehenny/auth
@sagehenny/entitlements
@sagehenny/themes
@sagehenny/audit
@sagehenny/agents
@sagehenny/identity
@sagehenny/release-gates
@sagehenny/sdk

Secure interfaces for products to request entitlements, tenant configuration, theme data, package access, agent capabilities, and platform events.

Signed events for license changes, tenant updates, releases, package changes, billing events, and security actions.

Dedicated test environments with isolated credentials, synthetic data, mock integrations, and promotion gates.

Product-specific tokens, environment restrictions, rotation, revocation, rate limits, and request auditing.

Versioned integration guides, examples, schemas, changelogs, compatibility information, and migration instructions.

Integration flow

Products ask SageHenny for decisions. SageHenny returns signed answers.

Product
SageHenny SDK
Authenticated request
SageHenny Control
Signed response
Product execution

Example requests

Check entitlement
Fetch theme
Validate tenant
Request package access
Read feature flags
Emit audit event

Documentation

API docs, SDKs, and policies.

Authenticated APIs only. Sandbox credentials never reach production.

API reference

Browse versioned endpoint stubs and scope rules.

Open docs

SDKs

Contract-aligned client libraries and packaging notes.

View SDKs

Policies

No password grant, PKCE required, broad scopes denied.

Read policies

Status & changelog

Operational status stubs and version change history.

Status · Changelog

Conceptual future SDK example

This package is not currently published. The example shows intended direction only.

import { createSageHennyClient } from "@sagehenny/sdk";

const sage = createSageHennyClient({
  product: "logiiq",
  environment: "production",
  token: process.env.SAGEHENNY_PRODUCT_TOKEN,
});

const entitlement = await sage.entitlements.check({
  tenantId,
  capability: "wms.problem-solving",
});

if (!entitlement.allowed) {
  throw new Error("Capability not enabled");
}

Developer principles

Least privilege

Tokens, packages, and APIs should grant only the access a product genuinely needs.

Versioned contracts

Integrations should evolve through explicit versions, compatibility rules, and clear migration paths.

Explicit approvals

Sensitive capabilities should remain gated by review, permission, and accountable decision records.

Complete auditability

Requests, changes, and executions should leave a durable trail that can be explained later.

The developer platform starts private and earns its way outward.

SageHenny will first prove its packages, APIs, agents, and release controls across its own products before opening broader access.

Read our principles