@agentchatme/openclaw 0.2.0 → 0.3.0

package/dist/index.d.cts

@@ -1,129 +1,32 @@
-import { A as AgentchatChannelConfig } from './setup-entry-CU0vHfyd.cjs';
-export { a as AGENTCHAT_CHANNEL_ID, b as AGENTCHAT_DEFAULT_ACCOUNT_ID, c as AgentchatResolvedAccount, d as agentchatChannelEntry, e as agentchatPlugin, f as agentchatSetupEntry, e as agentchatSetupPlugin, d as default, p as parseChannelConfig } from './setup-entry-CU0vHfyd.cjs';
-import { ChannelSetupWizard } from 'openclaw/plugin-sdk/channel-setup';
+import { A as AgentchatChannelConfig } from './setup-entry-1vjPD1gu.cjs';
+export { a as AgentchatResolvedAccount, b as agentchatChannelEntry, c as agentchatPlugin, d as agentchatSetupEntry, c as agentchatSetupPlugin, b as default, p as parseChannelConfig } from './setup-entry-1vjPD1gu.cjs';
 export { hasAgentChatConfiguredState } from './configured-state.cjs';
 import { WebSocket } from 'ws';
 import 'openclaw/plugin-sdk/channel-core';
 import 'zod';
 
 /**
- * Minimal HTTP client used by the setup plugin (P7) to:
- *   - verify an API key is live before finalizing setup (`validateApiKey`)
- *   - drive the email-OTP self-registration flow for agents without a key yet
- *     (`registerAgentStart` → `registerAgentVerify`)
- *
- * Why this lives separately from `outbound.ts`:
- *   - `outbound.ts` is the hot-path message sender. It wants retries, a circuit
- *     breaker, metrics, and a long-lived `fetch`. Setup is one-shot, low-rate,
- *     user-interactive — a 200ms validation call doesn't need any of that.
- *   - Setup runs before the runtime exists; coupling it to `OutboundAdapter`
- *     (which expects a parsed `AgentchatChannelConfig`) would force an odd
- *     partial-config path during registration.
- *
- * The server endpoints this module targets are stable AgentChat REST calls:
- *   - `GET  /v1/agents/me`          → 200 OK when the key authenticates
- *   - `POST /v1/register`           → 200 with `{ pending_id }`
- *   - `POST /v1/register/verify`    → 201 with `{ agent, api_key }` on success
- *
- * All methods return strongly-typed result unions — setup UIs can `switch` on
- * the discriminant without guessing at HTTP status codes.
- */
-/** Subset of the AgentChat agent row the setup surface needs to show the user. */
-interface AgentchatAgentIdentity {
-    readonly handle: string;
-    readonly displayName: string | null;
-    readonly email: string;
-    readonly createdAt: string;
-}
-type ValidateApiKeyResult = {
-    readonly ok: true;
-    readonly agent: AgentchatAgentIdentity;
-} | {
-    readonly ok: false;
-    /** High-level reason code the UI can map to a localized message. */
-    readonly reason: 'unauthorized' | 'forbidden' | 'deleted' | 'network-error' | 'unreachable' | 'server-error' | 'unexpected-shape';
-    readonly message: string;
-    readonly status?: number;
-};
-interface ValidateApiKeyOptions {
-    readonly apiBase?: string;
-    readonly fetch?: typeof fetch;
-    readonly timeoutMs?: number;
-}
-/**
- * Probe the API key against `GET /v1/agents/me`. Returns a discriminated
- * result — never throws on HTTP or network errors. The caller decides how
- * to surface each failure mode to the user.
- */
-declare function validateApiKey(apiKey: string, opts?: ValidateApiKeyOptions): Promise<ValidateApiKeyResult>;
-interface RegisterAgentStartInput {
-    readonly email: string;
-    readonly handle: string;
-    readonly displayName?: string;
-    readonly description?: string;
-}
-type RegisterStartResult = {
-    readonly ok: true;
-    readonly pendingId: string;
-} | {
-    readonly ok: false;
-    readonly reason: 'invalid-handle' | 'handle-taken' | 'email-taken' | 'email-is-owner' | 'email-exhausted' | 'rate-limited' | 'otp-failed' | 'network-error' | 'server-error' | 'validation';
-    readonly message: string;
-    readonly status?: number;
-    readonly retryAfterSeconds?: number;
-};
-interface RegisterAgentVerifyInput {
-    readonly pendingId: string;
-    readonly code: string;
-}
-type RegisterVerifyResult = {
-    readonly ok: true;
-    readonly apiKey: string;
-    readonly agent: AgentchatAgentIdentity;
-} | {
-    readonly ok: false;
-    readonly reason: 'expired' | 'invalid-code' | 'rate-limited' | 'handle-taken' | 'email-taken' | 'email-is-owner' | 'network-error' | 'server-error' | 'unexpected-shape' | 'validation';
-    readonly message: string;
-    readonly status?: number;
-    readonly retryAfterSeconds?: number;
-};
-interface RegisterOptions {
-    readonly apiBase?: string;
-    readonly fetch?: typeof fetch;
-    readonly timeoutMs?: number;
-}
-/**
- * Kick off an email-OTP registration. Server caches the intent under a
- * `pending_id` for 10 minutes and emails a 6-digit code to `email`.
- */
-declare function registerAgentStart(input: RegisterAgentStartInput, opts?: RegisterOptions): Promise<RegisterStartResult>;
-/** Verify the OTP the user received by email and mint the API key. */
-declare function registerAgentVerify(input: RegisterAgentVerifyInput, opts?: RegisterOptions): Promise<RegisterVerifyResult>;
-/**
- * Throw-flavored wrapper used by callers that prefer exception control flow
- * (the setup plugin's `afterAccountConfigWritten` hook). Converts a failure
- * result into an `AgentChatChannelError` with an appropriate class.
- */
-declare function assertApiKeyValid(apiKey: string, opts?: ValidateApiKeyOptions): Promise<AgentchatAgentIdentity>;
-
-/**
- * Interactive setup wizard for the AgentChat channel.
- *
- * Invoked by `openclaw channels add --channel agentchat`. Drives three branches:
- *
- *   - edit     — existing config → re-validate OR rotate OR change API base
- *   - have-key — user pastes an existing ac_live_* key → /agents/me probe → write
- *   - register — email + handle + description → /register + OTP → /register/verify
+ * Account-config primitives for the AgentChat channel plugin.
  *
- * All branches converge on `writeAccountPatch` which mutates
- * `channels.agentchat.<accountId>` in either flat or multi-account form.
+ * This module owns the smallest set of shared pieces that both the plugin
+ * definition (`channel.ts`) and the interactive setup wizard
+ * (`channel.wizard.ts`) need to read or mutate the `channels.agentchat.*`
+ * section of the OpenClaw config. Keeping them in a leaf file (no imports
+ * from other channel-* modules) breaks the channel.ts ↔ channel.wizard.ts
+ * import cycle — without it, the wizard literal's `channel:` field resolves
+ * to the temporal-dead-zone value of `AGENTCHAT_CHANNEL_ID` at module-init
+ * time, which bundlers emit as `undefined`.
  *
- * Every server-side failure mode surfaces as actionable copy — there are no
- * silent failures. The wizard only returns when the user has either finished
- * or explicitly chosen to abort.
+ * Invariants:
+ *   - Flat form (`channels.agentchat.{apiKey,...}`) is the default-account
+ *     layout when no `accounts` key is present. Once a named account is
+ *     written, flat form is never used again for the default account.
+ *   - The `enabled` flag is section-level (not per-account) and is kept out
+ *     of the Zod-parsed account shape because the schema is `.strict()`.
  */
 
-declare const agentchatSetupWizard: ChannelSetupWizard;
+declare const AGENTCHAT_CHANNEL_ID: "agentchat";
+declare const AGENTCHAT_DEFAULT_ACCOUNT_ID = "default";
 
 interface Logger {
     trace(obj: object, msg?: string): void;
@@ -753,4 +656,104 @@ declare class AgentchatChannelRuntime {
     private recordInboundMetric;
 }
 
-export { AgentChatChannelError, type AgentchatAgentIdentity, AgentchatChannelConfig, AgentchatChannelRuntime, type ChannelRuntimeHandlers, type ChannelRuntimeOptions, type ConnectionState, type ConversationKind, type ErrorClass, type HealthSnapshot, type Message, type MessageContent, type MessageStatus, type MessageType, type NormalizedGroupDeleted, type NormalizedGroupInvite, type NormalizedInbound, type NormalizedMessage, type NormalizedPresence, type NormalizedRateLimitWarning, type NormalizedReadReceipt, type NormalizedTyping, type NormalizedUnknown, type OutboundBacklogWarning, type OutboundDirectMessage, type OutboundGroupMessage, type OutboundMessageInput, type RegisterAgentStartInput, type RegisterAgentVerifyInput, type RegisterOptions, type RegisterStartResult, type RegisterVerifyResult, type SendResult, type ValidateApiKeyOptions, type ValidateApiKeyResult, agentchatSetupWizard, assertApiKeyValid, registerAgentStart, registerAgentVerify, validateApiKey };
+/**
+ * Minimal HTTP client used by the setup plugin (P7) to:
+ *   - verify an API key is live before finalizing setup (`validateApiKey`)
+ *   - drive the email-OTP self-registration flow for agents without a key yet
+ *     (`registerAgentStart` → `registerAgentVerify`)
+ *
+ * Why this lives separately from `outbound.ts`:
+ *   - `outbound.ts` is the hot-path message sender. It wants retries, a circuit
+ *     breaker, metrics, and a long-lived `fetch`. Setup is one-shot, low-rate,
+ *     user-interactive — a 200ms validation call doesn't need any of that.
+ *   - Setup runs before the runtime exists; coupling it to `OutboundAdapter`
+ *     (which expects a parsed `AgentchatChannelConfig`) would force an odd
+ *     partial-config path during registration.
+ *
+ * The server endpoints this module targets are stable AgentChat REST calls:
+ *   - `GET  /v1/agents/me`          → 200 OK when the key authenticates
+ *   - `POST /v1/register`           → 200 with `{ pending_id }`
+ *   - `POST /v1/register/verify`    → 201 with `{ agent, api_key }` on success
+ *
+ * All methods return strongly-typed result unions — setup UIs can `switch` on
+ * the discriminant without guessing at HTTP status codes.
+ */
+/** Subset of the AgentChat agent row the setup surface needs to show the user. */
+interface AgentchatAgentIdentity {
+    readonly handle: string;
+    readonly displayName: string | null;
+    readonly email: string;
+    readonly createdAt: string;
+}
+type ValidateApiKeyResult = {
+    readonly ok: true;
+    readonly agent: AgentchatAgentIdentity;
+} | {
+    readonly ok: false;
+    /** High-level reason code the UI can map to a localized message. */
+    readonly reason: 'unauthorized' | 'forbidden' | 'deleted' | 'network-error' | 'unreachable' | 'server-error' | 'unexpected-shape';
+    readonly message: string;
+    readonly status?: number;
+};
+interface ValidateApiKeyOptions {
+    readonly apiBase?: string;
+    readonly fetch?: typeof fetch;
+    readonly timeoutMs?: number;
+}
+/**
+ * Probe the API key against `GET /v1/agents/me`. Returns a discriminated
+ * result — never throws on HTTP or network errors. The caller decides how
+ * to surface each failure mode to the user.
+ */
+declare function validateApiKey(apiKey: string, opts?: ValidateApiKeyOptions): Promise<ValidateApiKeyResult>;
+interface RegisterAgentStartInput {
+    readonly email: string;
+    readonly handle: string;
+    readonly displayName?: string;
+    readonly description?: string;
+}
+type RegisterStartResult = {
+    readonly ok: true;
+    readonly pendingId: string;
+} | {
+    readonly ok: false;
+    readonly reason: 'invalid-handle' | 'handle-taken' | 'email-taken' | 'email-exhausted' | 'rate-limited' | 'otp-failed' | 'network-error' | 'server-error' | 'validation';
+    readonly message: string;
+    readonly status?: number;
+    readonly retryAfterSeconds?: number;
+};
+interface RegisterAgentVerifyInput {
+    readonly pendingId: string;
+    readonly code: string;
+}
+type RegisterVerifyResult = {
+    readonly ok: true;
+    readonly apiKey: string;
+    readonly agent: AgentchatAgentIdentity;
+} | {
+    readonly ok: false;
+    readonly reason: 'expired' | 'invalid-code' | 'rate-limited' | 'handle-taken' | 'email-taken' | 'network-error' | 'server-error' | 'unexpected-shape' | 'validation';
+    readonly message: string;
+    readonly status?: number;
+    readonly retryAfterSeconds?: number;
+};
+interface RegisterOptions {
+    readonly apiBase?: string;
+    readonly fetch?: typeof fetch;
+    readonly timeoutMs?: number;
+}
+/**
+ * Kick off an email-OTP registration. Server caches the intent under a
+ * `pending_id` for 10 minutes and emails a 6-digit code to `email`.
+ */
+declare function registerAgentStart(input: RegisterAgentStartInput, opts?: RegisterOptions): Promise<RegisterStartResult>;
+/** Verify the OTP the user received by email and mint the API key. */
+declare function registerAgentVerify(input: RegisterAgentVerifyInput, opts?: RegisterOptions): Promise<RegisterVerifyResult>;
+/**
+ * Throw-flavored wrapper used by callers that prefer exception control flow
+ * (the setup plugin's `afterAccountConfigWritten` hook). Converts a failure
+ * result into an `AgentChatChannelError` with an appropriate class.
+ */
+declare function assertApiKeyValid(apiKey: string, opts?: ValidateApiKeyOptions): Promise<AgentchatAgentIdentity>;
+
+export { AGENTCHAT_CHANNEL_ID, AGENTCHAT_DEFAULT_ACCOUNT_ID, AgentChatChannelError, type AgentchatAgentIdentity, AgentchatChannelConfig, AgentchatChannelRuntime, type ChannelRuntimeHandlers, type ChannelRuntimeOptions, type ConnectionState, type ConversationKind, type ErrorClass, type HealthSnapshot, type Message, type MessageContent, type MessageStatus, type MessageType, type NormalizedGroupDeleted, type NormalizedGroupInvite, type NormalizedInbound, type NormalizedMessage, type NormalizedPresence, type NormalizedRateLimitWarning, type NormalizedReadReceipt, type NormalizedTyping, type NormalizedUnknown, type OutboundBacklogWarning, type OutboundDirectMessage, type OutboundGroupMessage, type OutboundMessageInput, type RegisterAgentStartInput, type RegisterAgentVerifyInput, type RegisterOptions, type RegisterStartResult, type RegisterVerifyResult, type SendResult, type ValidateApiKeyOptions, type ValidateApiKeyResult, assertApiKeyValid, registerAgentStart, registerAgentVerify, validateApiKey };

package/dist/index.d.ts

@@ -1,129 +1,32 @@
-import { A as AgentchatChannelConfig } from './setup-entry-CU0vHfyd.js';
-export { a as AGENTCHAT_CHANNEL_ID, b as AGENTCHAT_DEFAULT_ACCOUNT_ID, c as AgentchatResolvedAccount, d as agentchatChannelEntry, e as agentchatPlugin, f as agentchatSetupEntry, e as agentchatSetupPlugin, d as default, p as parseChannelConfig } from './setup-entry-CU0vHfyd.js';
-import { ChannelSetupWizard } from 'openclaw/plugin-sdk/channel-setup';
+import { A as AgentchatChannelConfig } from './setup-entry-1vjPD1gu.js';
+export { a as AgentchatResolvedAccount, b as agentchatChannelEntry, c as agentchatPlugin, d as agentchatSetupEntry, c as agentchatSetupPlugin, b as default, p as parseChannelConfig } from './setup-entry-1vjPD1gu.js';
 export { hasAgentChatConfiguredState } from './configured-state.js';
 import { WebSocket } from 'ws';
 import 'openclaw/plugin-sdk/channel-core';
 import 'zod';
 
 /**
- * Minimal HTTP client used by the setup plugin (P7) to:
- *   - verify an API key is live before finalizing setup (`validateApiKey`)
- *   - drive the email-OTP self-registration flow for agents without a key yet
- *     (`registerAgentStart` → `registerAgentVerify`)
- *
- * Why this lives separately from `outbound.ts`:
- *   - `outbound.ts` is the hot-path message sender. It wants retries, a circuit
- *     breaker, metrics, and a long-lived `fetch`. Setup is one-shot, low-rate,
- *     user-interactive — a 200ms validation call doesn't need any of that.
- *   - Setup runs before the runtime exists; coupling it to `OutboundAdapter`
- *     (which expects a parsed `AgentchatChannelConfig`) would force an odd
- *     partial-config path during registration.
- *
- * The server endpoints this module targets are stable AgentChat REST calls:
- *   - `GET  /v1/agents/me`          → 200 OK when the key authenticates
- *   - `POST /v1/register`           → 200 with `{ pending_id }`
- *   - `POST /v1/register/verify`    → 201 with `{ agent, api_key }` on success
- *
- * All methods return strongly-typed result unions — setup UIs can `switch` on
- * the discriminant without guessing at HTTP status codes.
- */
-/** Subset of the AgentChat agent row the setup surface needs to show the user. */
-interface AgentchatAgentIdentity {
-    readonly handle: string;
-    readonly displayName: string | null;
-    readonly email: string;
-    readonly createdAt: string;
-}
-type ValidateApiKeyResult = {
-    readonly ok: true;
-    readonly agent: AgentchatAgentIdentity;
-} | {
-    readonly ok: false;
-    /** High-level reason code the UI can map to a localized message. */
-    readonly reason: 'unauthorized' | 'forbidden' | 'deleted' | 'network-error' | 'unreachable' | 'server-error' | 'unexpected-shape';
-    readonly message: string;
-    readonly status?: number;
-};
-interface ValidateApiKeyOptions {
-    readonly apiBase?: string;
-    readonly fetch?: typeof fetch;
-    readonly timeoutMs?: number;
-}
-/**
- * Probe the API key against `GET /v1/agents/me`. Returns a discriminated
- * result — never throws on HTTP or network errors. The caller decides how
- * to surface each failure mode to the user.
- */
-declare function validateApiKey(apiKey: string, opts?: ValidateApiKeyOptions): Promise<ValidateApiKeyResult>;
-interface RegisterAgentStartInput {
-    readonly email: string;
-    readonly handle: string;
-    readonly displayName?: string;
-    readonly description?: string;
-}
-type RegisterStartResult = {
-    readonly ok: true;
-    readonly pendingId: string;
-} | {
-    readonly ok: false;
-    readonly reason: 'invalid-handle' | 'handle-taken' | 'email-taken' | 'email-is-owner' | 'email-exhausted' | 'rate-limited' | 'otp-failed' | 'network-error' | 'server-error' | 'validation';
-    readonly message: string;
-    readonly status?: number;
-    readonly retryAfterSeconds?: number;
-};
-interface RegisterAgentVerifyInput {
-    readonly pendingId: string;
-    readonly code: string;
-}
-type RegisterVerifyResult = {
-    readonly ok: true;
-    readonly apiKey: string;
-    readonly agent: AgentchatAgentIdentity;
-} | {
-    readonly ok: false;
-    readonly reason: 'expired' | 'invalid-code' | 'rate-limited' | 'handle-taken' | 'email-taken' | 'email-is-owner' | 'network-error' | 'server-error' | 'unexpected-shape' | 'validation';
-    readonly message: string;
-    readonly status?: number;
-    readonly retryAfterSeconds?: number;
-};
-interface RegisterOptions {
-    readonly apiBase?: string;
-    readonly fetch?: typeof fetch;
-    readonly timeoutMs?: number;
-}
-/**
- * Kick off an email-OTP registration. Server caches the intent under a
- * `pending_id` for 10 minutes and emails a 6-digit code to `email`.
- */
-declare function registerAgentStart(input: RegisterAgentStartInput, opts?: RegisterOptions): Promise<RegisterStartResult>;
-/** Verify the OTP the user received by email and mint the API key. */
-declare function registerAgentVerify(input: RegisterAgentVerifyInput, opts?: RegisterOptions): Promise<RegisterVerifyResult>;
-/**
- * Throw-flavored wrapper used by callers that prefer exception control flow
- * (the setup plugin's `afterAccountConfigWritten` hook). Converts a failure
- * result into an `AgentChatChannelError` with an appropriate class.
- */
-declare function assertApiKeyValid(apiKey: string, opts?: ValidateApiKeyOptions): Promise<AgentchatAgentIdentity>;
-
-/**
- * Interactive setup wizard for the AgentChat channel.
- *
- * Invoked by `openclaw channels add --channel agentchat`. Drives three branches:
- *
- *   - edit     — existing config → re-validate OR rotate OR change API base
- *   - have-key — user pastes an existing ac_live_* key → /agents/me probe → write
- *   - register — email + handle + description → /register + OTP → /register/verify
+ * Account-config primitives for the AgentChat channel plugin.
  *
- * All branches converge on `writeAccountPatch` which mutates
- * `channels.agentchat.<accountId>` in either flat or multi-account form.
+ * This module owns the smallest set of shared pieces that both the plugin
+ * definition (`channel.ts`) and the interactive setup wizard
+ * (`channel.wizard.ts`) need to read or mutate the `channels.agentchat.*`
+ * section of the OpenClaw config. Keeping them in a leaf file (no imports
+ * from other channel-* modules) breaks the channel.ts ↔ channel.wizard.ts
+ * import cycle — without it, the wizard literal's `channel:` field resolves
+ * to the temporal-dead-zone value of `AGENTCHAT_CHANNEL_ID` at module-init
+ * time, which bundlers emit as `undefined`.
  *
- * Every server-side failure mode surfaces as actionable copy — there are no
- * silent failures. The wizard only returns when the user has either finished
- * or explicitly chosen to abort.
+ * Invariants:
+ *   - Flat form (`channels.agentchat.{apiKey,...}`) is the default-account
+ *     layout when no `accounts` key is present. Once a named account is
+ *     written, flat form is never used again for the default account.
+ *   - The `enabled` flag is section-level (not per-account) and is kept out
+ *     of the Zod-parsed account shape because the schema is `.strict()`.
  */
 
-declare const agentchatSetupWizard: ChannelSetupWizard;
+declare const AGENTCHAT_CHANNEL_ID: "agentchat";
+declare const AGENTCHAT_DEFAULT_ACCOUNT_ID = "default";
 
 interface Logger {
     trace(obj: object, msg?: string): void;
@@ -753,4 +656,104 @@ declare class AgentchatChannelRuntime {
     private recordInboundMetric;
 }
 
-export { AgentChatChannelError, type AgentchatAgentIdentity, AgentchatChannelConfig, AgentchatChannelRuntime, type ChannelRuntimeHandlers, type ChannelRuntimeOptions, type ConnectionState, type ConversationKind, type ErrorClass, type HealthSnapshot, type Message, type MessageContent, type MessageStatus, type MessageType, type NormalizedGroupDeleted, type NormalizedGroupInvite, type NormalizedInbound, type NormalizedMessage, type NormalizedPresence, type NormalizedRateLimitWarning, type NormalizedReadReceipt, type NormalizedTyping, type NormalizedUnknown, type OutboundBacklogWarning, type OutboundDirectMessage, type OutboundGroupMessage, type OutboundMessageInput, type RegisterAgentStartInput, type RegisterAgentVerifyInput, type RegisterOptions, type RegisterStartResult, type RegisterVerifyResult, type SendResult, type ValidateApiKeyOptions, type ValidateApiKeyResult, agentchatSetupWizard, assertApiKeyValid, registerAgentStart, registerAgentVerify, validateApiKey };
+/**
+ * Minimal HTTP client used by the setup plugin (P7) to:
+ *   - verify an API key is live before finalizing setup (`validateApiKey`)
+ *   - drive the email-OTP self-registration flow for agents without a key yet
+ *     (`registerAgentStart` → `registerAgentVerify`)
+ *
+ * Why this lives separately from `outbound.ts`:
+ *   - `outbound.ts` is the hot-path message sender. It wants retries, a circuit
+ *     breaker, metrics, and a long-lived `fetch`. Setup is one-shot, low-rate,
+ *     user-interactive — a 200ms validation call doesn't need any of that.
+ *   - Setup runs before the runtime exists; coupling it to `OutboundAdapter`
+ *     (which expects a parsed `AgentchatChannelConfig`) would force an odd
+ *     partial-config path during registration.
+ *
+ * The server endpoints this module targets are stable AgentChat REST calls:
+ *   - `GET  /v1/agents/me`          → 200 OK when the key authenticates
+ *   - `POST /v1/register`           → 200 with `{ pending_id }`
+ *   - `POST /v1/register/verify`    → 201 with `{ agent, api_key }` on success
+ *
+ * All methods return strongly-typed result unions — setup UIs can `switch` on
+ * the discriminant without guessing at HTTP status codes.
+ */
+/** Subset of the AgentChat agent row the setup surface needs to show the user. */
+interface AgentchatAgentIdentity {
+    readonly handle: string;
+    readonly displayName: string | null;
+    readonly email: string;
+    readonly createdAt: string;
+}
+type ValidateApiKeyResult = {
+    readonly ok: true;
+    readonly agent: AgentchatAgentIdentity;
+} | {
+    readonly ok: false;
+    /** High-level reason code the UI can map to a localized message. */
+    readonly reason: 'unauthorized' | 'forbidden' | 'deleted' | 'network-error' | 'unreachable' | 'server-error' | 'unexpected-shape';
+    readonly message: string;
+    readonly status?: number;
+};
+interface ValidateApiKeyOptions {
+    readonly apiBase?: string;
+    readonly fetch?: typeof fetch;
+    readonly timeoutMs?: number;
+}
+/**
+ * Probe the API key against `GET /v1/agents/me`. Returns a discriminated
+ * result — never throws on HTTP or network errors. The caller decides how
+ * to surface each failure mode to the user.
+ */
+declare function validateApiKey(apiKey: string, opts?: ValidateApiKeyOptions): Promise<ValidateApiKeyResult>;
+interface RegisterAgentStartInput {
+    readonly email: string;
+    readonly handle: string;
+    readonly displayName?: string;
+    readonly description?: string;
+}
+type RegisterStartResult = {
+    readonly ok: true;
+    readonly pendingId: string;
+} | {
+    readonly ok: false;
+    readonly reason: 'invalid-handle' | 'handle-taken' | 'email-taken' | 'email-exhausted' | 'rate-limited' | 'otp-failed' | 'network-error' | 'server-error' | 'validation';
+    readonly message: string;
+    readonly status?: number;
+    readonly retryAfterSeconds?: number;
+};
+interface RegisterAgentVerifyInput {
+    readonly pendingId: string;
+    readonly code: string;
+}
+type RegisterVerifyResult = {
+    readonly ok: true;
+    readonly apiKey: string;
+    readonly agent: AgentchatAgentIdentity;
+} | {
+    readonly ok: false;
+    readonly reason: 'expired' | 'invalid-code' | 'rate-limited' | 'handle-taken' | 'email-taken' | 'network-error' | 'server-error' | 'unexpected-shape' | 'validation';
+    readonly message: string;
+    readonly status?: number;
+    readonly retryAfterSeconds?: number;
+};
+interface RegisterOptions {
+    readonly apiBase?: string;
+    readonly fetch?: typeof fetch;
+    readonly timeoutMs?: number;
+}
+/**
+ * Kick off an email-OTP registration. Server caches the intent under a
+ * `pending_id` for 10 minutes and emails a 6-digit code to `email`.
+ */
+declare function registerAgentStart(input: RegisterAgentStartInput, opts?: RegisterOptions): Promise<RegisterStartResult>;
+/** Verify the OTP the user received by email and mint the API key. */
+declare function registerAgentVerify(input: RegisterAgentVerifyInput, opts?: RegisterOptions): Promise<RegisterVerifyResult>;
+/**
+ * Throw-flavored wrapper used by callers that prefer exception control flow
+ * (the setup plugin's `afterAccountConfigWritten` hook). Converts a failure
+ * result into an `AgentChatChannelError` with an appropriate class.
+ */
+declare function assertApiKeyValid(apiKey: string, opts?: ValidateApiKeyOptions): Promise<AgentchatAgentIdentity>;
+
+export { AGENTCHAT_CHANNEL_ID, AGENTCHAT_DEFAULT_ACCOUNT_ID, AgentChatChannelError, type AgentchatAgentIdentity, AgentchatChannelConfig, AgentchatChannelRuntime, type ChannelRuntimeHandlers, type ChannelRuntimeOptions, type ConnectionState, type ConversationKind, type ErrorClass, type HealthSnapshot, type Message, type MessageContent, type MessageStatus, type MessageType, type NormalizedGroupDeleted, type NormalizedGroupInvite, type NormalizedInbound, type NormalizedMessage, type NormalizedPresence, type NormalizedRateLimitWarning, type NormalizedReadReceipt, type NormalizedTyping, type NormalizedUnknown, type OutboundBacklogWarning, type OutboundDirectMessage, type OutboundGroupMessage, type OutboundMessageInput, type RegisterAgentStartInput, type RegisterAgentVerifyInput, type RegisterOptions, type RegisterStartResult, type RegisterVerifyResult, type SendResult, type ValidateApiKeyOptions, type ValidateApiKeyResult, assertApiKeyValid, registerAgentStart, registerAgentVerify, validateApiKey };