Developer Platform

Embed governed AI agents without rebuilding the runtime layer.

AgentShelf gives developers SDKs, widget embeds, headless runtime APIs, and integration patterns for bringing governed agents into websites, products, workflows, and external applications.

Review SDK examples

Drop-in embed

WidgetSDKREST

<script
  async
  src="https://app.agentshelf.ai/widget.js"
  data-site-id="widget_site_id"
></script>

The hosted widget is one script tag. The SDK and headless API cover custom UIs.

  • Widget embeds
  • Headless APIs
  • SDK access
  • Public runtime sessions
  • Usage telemetry

Runtime surfaces

One agent runtime, multiple ways to deploy.

Use the surface that matches the experience you are building while keeping each individual agent connected to the same AgentShelf control plane.

Standard widget embed

Add a hosted website agent with the existing widget script when you want the AgentShelf-provided shell, launcher, and visitor experience.

  • Best for website AI front desks, visitor questions, lead capture, and support handoff.

Headless widget API

Use the browser SDK and public headless runtime when you want to design your own chat UI while relying on AgentShelf for sessions and streaming.

  • Best for custom website chat, branded support surfaces, and embedded product workflows.

SDK-based product embedding

Build custom agent interfaces with SDK access to sessions, streamed responses, visitor identity, page traces, and lead capture helpers.

  • Best for frontend teams building bespoke agent experiences inside web applications.

API-backed integrations

Connect agent experiences to external systems and workflows through approved runtime patterns instead of wiring every application directly to model providers.

  • Best for portals, partner apps, workflow tools, and system-backed agent experiences.

Runtime boundaries

Separate public experiences from authenticated platform controls.

The agent harness—the managed layer around execution—can keep public sessions connected to configured origin checks, access controls, telemetry, and usage tracking without exposing administrative controls.

Public surface

Public runtime traffic

Website widgets, headless public sessions, visitor identity, page context, lead capture, and engagement events.

Shared control

Governed runtime

Model routing, usage telemetry, policies, runtime events, traces, and attribution connect runtime activity to the platform.

Platform access

Authenticated controls

Agent configuration, admin controls, billing, workspaces, private context management, and governance settings.

Agent harness boundary

Website agent traffic stays separate from authenticated platform administration while remaining connected to configured runtime controls and records. Evaluating a public or embedded agent experience? See how authenticated control, the dedicated workspace, and the supported public experience remain distinct. Explore Trust & Boundaries

SDK access

Build custom interfaces on top of the AgentShelf widget runtime.

The browser-first AgentShelf widget SDK gives frontend developers access to the headless widget runtime without forcing the standard iframe, modal, launcher, or default UI shell.

  • Create or restore visitor sessions.
  • Stream assistant responses into your own UI.
  • Render lead forms selected by the runtime.
  • Collect browser attribution and page trace events.
  • Use storage adapters for custom session persistence.
import { createWidgetClient } from '@agentshelf/widget-sdk'; const client = createWidgetClient({  siteId: 'widget_site_id',}); await client.ensureSession({  visitorFingerprint: 'anon-visitor-123',});

Integration patterns

Bring agents into the surfaces your users already use.

Developers can create custom frontends, stream responses, pass approved external context, handle client-side continuations, and capture structured lead or workflow data through supported runtime APIs.

Custom chat UI

Render your own transcript, inputs, quick replies, streaming states, and errors while AgentShelf manages runtime sessions.

In-product assistant

Embed an AgentShelf-powered agent inside a product workflow, portal, or customer experience.

Lead capture flow

Use runtime form signals and lead capture helpers to collect contact details, route follow-up, and preserve conversation context.

Proactive engagement

Evaluate configured engagement gates and show contextual prompts from your own UI.

External context

Pass approved external context from the host app while keeping public sessions separate from administrative platform access.

Client-side tools

Handle tool calls in the host application and continue the same assistant turn with validated tool results.

Trust layer

Designed for governed public and embedded agent experiences.

Developer integrations are designed to keep authenticated controls inside the platform, public runtime sessions within configured boundaries, and runtime activity available for review.

Origin and access checks

Use configured origins, expected host applications, and access rules to limit public runtime access.

Guarded responses

Support public-facing agent behavior with approved configuration and response patterns.

Runtime telemetry

Use available runtime traces, usage records, and event visibility for debugging and governance review.

Public runtime boundary

Public-facing agents use managed runtime sessions with configured telemetry, routing, and governance while private workspace access stays behind authenticated platform controls.

Design the agent experience. Use AgentShelf for the runtime.

Bring AgentShelf-powered agents into your website, product, portal, or workflow without rebuilding session management, streaming, engagement, lead capture, telemetry, model routing, and governance infrastructure from scratch.

Explore Agent Builder