MoonKeyDocumentation
Foundation

Core concepts

The durable product objects behind every MoonKey integration.

Foundation implemented
Pre-alpha documentation boundary

Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.

Examples
Code example format

Tenant hierarchy#

MoonKey scopes authority through organization, environment, ecosystem, and application. Production, staging, and development never share wallet namespaces by default.

Hierarchy
Organization
└── Environment
    └── Ecosystem
        └── Application
            └── App-bound session

Identity and credentials#

An identity can own several independently revocable credentials. Credentials prove access; they do not provide wallet key entropy and are not silently merged through display-email equality.

  • Provider subjects preferred
  • Scoped HMAC lookup digests
  • Credential linking requires proof
  • Wallet ownership survives credential replacement

Wallet scope#

Application scope creates a namespace for one app. Ecosystem scope creates one namespace shared by approved apps in an entitled ecosystem. A missing ecosystem entitlement is an error, never an implicit downgrade.

TypeScript
type WalletScope = "application" | "ecosystem";

// A client requests scope; it never authorizes scope.
// The server reloads app context and effective entitlements.
const required = {
  application: ["wallet_scope.application"],
  ecosystem: [
    "wallet_scope.ecosystem",
    "ecosystem.multi_app",
  ],
} as const;
Implementation status

Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.

Engineering status

Command center

Search page titles and navigate to a console page or documentation article.