SDK overview

Axowl ships two SDK families. Most web apps use the JS/TS one; .NET services use the .NET clients.

JavaScript / TypeScript (`axowl-sdk` repo)

Package	Purpose
`@axowl/sdk`	React hooks & components — `AxowlProvider`, `useAxowl`, `usePermission`, `useSession`, `useOrg`
`@axowl/sdk-backend`	Express & Next.js middleware — `axowlMiddleware`, `requirePermission`, `getAuth`, `canAccess`
`@axowl/sdk-core`	Shared core (used internally)
`@axowl/sdk-wasm`	WASM integrity-verification core (`packages/sdk-wasm`)

import { AxowlProvider, useAxowl, usePermission } from '@axowl/sdk';

<AxowlProvider orgSlug="my-org" appKey="ak_live_xxxxx"><App /></AxowlProvider>

const { user, isSignedIn, signIn } = useAxowl();
const { can } = usePermission();           // can('dashboard.view')

Features (per axowl-sdk/README.md): magic-link, social (Google/Line), passkey (FIDO2), federated (OIDC); JWT auto-refresh; wildcard permission matching; React hooks; Express/Next middleware.

.NET (`Axowl.Sdk.*`, this repo)

Project	Purpose	Page
`Axowl.Sdk.Identity.Client`	Introspection, permission checks, `[RequirePermission]`	Identity ✅
`Axowl.Sdk.Integrity.Client`	Verify sealed records (REST/gRPC/Fallback)	Integrity
`Axowl.Sdk.Eventing.Client`	Subscribe / emit sealed events	Eventing
`Axowl.Sdk.Korean.Identity.Client`	`[RequireKoreanIdentity]` gating	Korean Identity

Each client uses a 3-layer transport (REST + gRPC over h2c + fallback), confirmed by the Rest*Client / Grpc*Client / Fallback*Client files in each project.

SDK overview

JavaScript / TypeScript (axowl-sdk repo)

.NET (Axowl.Sdk.*, this repo)

JavaScript / TypeScript (`axowl-sdk` repo)

.NET (`Axowl.Sdk.*`, this repo)