Bayon AI logo
BAYON AI

NPM packages for Bayon AI products

Build products on shared packages for APIs, design, analytics, authentication, notifications, email, MCP, gamification, offline storage, document editing, and agent contracts—without copying infrastructure between apps.

Browse NPM packagesOpen text editor docs

Choose an NPM package

Find the reusable layer your product needs, then review its installation, usage, integration contract, and host-owned boundaries before adopting it.

NPM Packages

Choose a package to review its purpose, installation, usage, integration contract, and boundaries. Dedicated documentation appears when available.

Published
v0.3.0

@bayonai/sdk

TypeScript SDK for the BayonAI Firebase API and product integrations.

NPM
Published
v1.0.3

@bayonai/rich-text-editor

Reusable rich-text document utilities, native React editing components, and unsaved-change session controls.

DocsNPM
Published
v0.1.1

@bayonai/offline

Reusable offline read-cache and pending-write primitives for Bayon AI apps.

NPM
Published
v0.1.3

@bayonai/analytics

Shared Bayon AI analytics and Next.js log-export adapter with PostHog provider support.

NPM
Published
v0.3.0

@bayonai/firebase-auth

Reusable Firebase authentication actions, React provider, MUI login surfaces, and server-owned email Functions.

NPM
Published
v0.1.2

@bayonai/push-notifications

Provider-neutral notification contracts with Capacitor Firebase, local notification, and Firebase Admin adapters.

NPM
Published
v0.1.1

@bayonai/transactional-email

Provider-neutral transactional email delivery with branded, overridable HTML and text templates.

NPM
Published
v0.1.2

@bayonai/transactional-email-firebase

Firebase Functions, Firestore mail operations, and an MUI admin surface for transactional email.

NPM
Published
v0.1.0

@bayonai/mcp

Shared OAuth, PKCE, bearer-challenge, and secret helpers for remote Model Context Protocol servers.

NPM
Published
v0.1.0

@bayonai/gamify

Storage-agnostic progress, goal, rank, and contextual-guidance primitives for Bayon AI applications.

NPM
Internal
v0.1.0

@bayonai/website-agent

Shared public and internal Bayon AI agent contracts for website chat and operator workflows.

Published
v1.0.0

@bayonai/mui-design

Shared Bayon AI Material UI theme, tokens, page recipes, and reusable React surfaces.

NPM

@bayonai/sdk

TypeScript SDK for the BayonAI Firebase API and product integrations.

NPM

Use this package when a Bayon AI product, integration, or automation needs typed access to the shared Firebase API surface without copying request helpers across apps.

  • Typed client surface for Bayon AI API route groups
  • ESM and CommonJS package outputs for browser, Node, and Functions consumers
  • Shared request contracts for conversations, agents, users, feedback, subscriptions, and admin workflows
  • Short-lived external-user tokens and direct audio-upload helpers for approved transcription flows

Package

@bayonai/sdk

Current version: v0.3.0

Source: npm:@bayonai/sdk

Boundaries

  • Does not host or deploy the Firebase API.
  • Does not own product authentication state.
  • Does not replace app-level validation or user-facing error handling.
  • Does not decide which API routes are exposed to public clients.

Install

npm install @bayonai/sdk

Verification or workspace command:

npm view @bayonai/sdk version

Usage

import { createBayonAiClient } from '@bayonai/sdk';

const bayonai = createBayonAiClient({
  apiKey: process.env.BAYONAI_API_KEY,
});

const response = await bayonai.conversations.send({
  personaId: 'journalapp',
  messages: [{ role: 'user', content: 'Hello' }],
});

Integration checklist

  1. Install the SDK in the app or server package that talks to the Bayon AI API.
  2. Configure the client from environment-owned credentials; endpoint updates arrive through SDK releases.
  3. Use per-request bearer tokens for external-user flows and keep organization API keys on trusted servers.
  4. Call typed route helpers from service modules, not directly from UI components.
  5. Keep API credentials server-side unless the route is explicitly safe for browser use.

Public contract

Consume the selected package contract directly instead of copying configuration into app components.

The SDK owns the deployed API endpoint so consumers only configure credentials

Route helpers keep request and response contracts centralized

Per-request bearer tokens support external-user flows without exposing an organization API key

Consumers own auth policy, retries, telemetry, and product-specific error presentation

Package releases should track API surface changes before downstream apps upgrade

Building a Bayon AI app surface?

Start with the shared package boundary that matches the product surface, then keep app-specific routing, auth policy, storage, and user-facing workflows in the consuming app.

Talk to Bayon AI