Public API Reference

SeldonFrame for developers, agents, and infrastructure teams.

Provision workspaces, manage encrypted secrets, ship blocks, query Brain context, and enable OpenClaw self-service from a clean, server-rendered API surface.

Auth

Builder keys, workspace keys, and secure secret capture.

Natural language

Seldon It responses return structured cards with deterministic actions.

Secure by default

Secrets are envelope encrypted and never requested in normal chat history.

Heads up

Builder routes use `x-seldon-api-key`. Workspace CRUD routes typically use `x-org-id` and `x-api-key`.

Create a workspace from one prompt

curl

curl -X POST https://app.seldonframe.com/api/v1/workspace/create \
  -H "Content-Type: application/json" \
  -H "x-seldon-api-key: $SELDONFRAME_API_KEY" \
  -H "x-claude-api-key: $CLAUDE_API_KEY" \
  -d '{
    "description": "AI coaching business for engineering leaders with booking, intake, and payment flows"
  }'

List managed workspaces

typescript

const response = await fetch("https://app.seldonframe.com/api/v1/workspaces", {
  headers: {
    "x-seldon-api-key": process.env.SELDONFRAME_API_KEY!,
  },
});

const payload = await response.json();
console.log(payload.workspaces);

Check Brain health

curl

curl https://app.seldonframe.com/api/v1/brain/health \
  -H "x-seldon-api-key: $SELDONFRAME_API_KEY"

Invite an end-client into self-service

curl

curl -X POST https://app.seldonframe.com/api/v1/portal/invite \
  -H "Content-Type: application/json" \
  -H "x-seldon-api-key: $SELDONFRAME_API_KEY" \
  -d '{
    "workspaceId": "ws_123",
    "contactId": "contact_456"
  }'
Access

Authentication

Seldon exposes two auth layers: builder-scoped APIs for workspace creation and orchestration, and workspace-scoped APIs for operational data access.

  • Use `x-seldon-api-key` for builder-level routes like workspace creation, managed workspace listing, self-service invites, and Brain health.
  • Use `x-api-key` plus `x-org-id` for workspace-scoped APIs like contacts, deals, forms, submissions, and webhooks.
  • Create personal API keys from Settings → API, and store third-party provider credentials through the secure secret flow instead of normal chat.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

Builder key

Header: x-seldon-api-key

Used for orchestration routes that operate across managed workspaces.

Workspace key

Headers: x-org-id + x-api-key

Used for per-workspace CRUD against contacts, deals, submissions, pages, and webhooks.

Secure secret flow

Masked capture only

Never paste provider secrets into chat history. Seldon stores them with envelope encryption and audit fields.

Provisioning

Workspaces

Create, enumerate, and inspect managed workspaces from a builder context. This is the fastest path from one prompt to a deployed business OS.

  • `POST /api/v1/workspace/create` accepts either a `description` or `url` plus a Claude BYOK header.
  • `GET /api/v1/workspaces` returns the managed workspace list for the current builder.
  • `GET /api/v1/workspace/:id` returns a normalized workspace record for one managed workspace.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

POST /api/v1/workspace/create

One-text creation

Returns `ready`, `split_required`, or `error` with dashboard and subdomain URLs when successful.

GET /api/v1/workspaces

Managed list

Use this to populate admin tooling, onboarding flows, or external orchestration runtimes.

GET /api/v1/workspace/:id

Workspace detail

Returns name, slug, subdomain, created timestamp, contact count, and ownership metadata.

Security

Secrets

Secrets are managed through Seldon-hosted secure capture flows. They are never requested in normal chat, never logged in plaintext, and stored encrypted at rest.

  • `store_secret` opens a dedicated masked capture flow and stores an encrypted workspace-scoped secret.
  • `list_secrets` returns metadata only: service name, fingerprint, key version, timestamps, and audit state.
  • `rotate_secret` invalidates the prior value and triggers a fresh secure capture flow.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

store_secret

Secure input only

Use for provider keys like Resend, Stripe, OpenAI, Anthropic, Twilio, and newsletter integrations.

list_secrets

Metadata only

Safe to surface inside Claude Code or OpenClaw because plaintext values never leave secure storage.

rotate_secret

Operational hygiene

Rotate credentials without exposing history and keep clear auditability for production workspaces.

Composable product surface

Blocks & Skills

Seldon treats pages, marketplace packages, and workflow blocks as composable primitives. You can list marketplace listings, publish new packages, and update page blocks over HTTP.

  • `GET /api/v1/marketplace/listings` lists the current workspace's creator listings.
  • `POST /api/v1/marketplace/listings` creates a new listing package from a soul package payload.
  • `GET /api/v1/pages/:pageId` and `PUT /api/v1/pages/:pageId` let you inspect or update rendered landing/page blocks.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

GET /api/v1/marketplace/listings

List blocks

Use this in builder tooling to show what skills or packages already exist for the current organization.

POST /api/v1/marketplace/listings

Create block package

Accepts listing metadata plus a soul package payload for marketplace-ready packaging.

PUT /api/v1/pages/:pageId

Update page block

Apply edits to a concrete page resource while keeping the surrounding CRM shell intact.

Natural language orchestration

Seldon It

Seldon It is the natural-language control plane for scoped changes. In HTTP flows, the end-client self-service route is the public natural-language endpoint; builder-mode orchestration is also available inside Claude Code and the dashboard.

  • `POST /api/v1/portal/self-service` accepts `orgSlug`, `description`, `portalToken`, and an optional `sessionId`.
  • Responses include `message`, `results`, `cards`, `suggestions`, and calm progress guidance for agentic clients.
  • Result cards standardize actions like Apply, Edit, Undo, and View live preview.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

POST /api/v1/portal/self-service

Scoped natural language

Send plain English and receive structured cards plus a persisted session id for follow-up requests.

Cards response

Agent friendly

Each response card includes a summary, preview URL, and deterministic actions for UI or bot rendering.

Progress cadence

15–20 seconds

Long-running clients like OpenClaw should surface one calm update roughly every 18 seconds.

Context and system intelligence

Brain

Brain endpoints let you pull workspace intelligence and operational health without exposing internal-only ops routes.

  • `GET /api/v1/brain/health` returns the current compiled Brain health summary for authenticated builders.
  • `GET /api/v1/soul/wiki` returns current workspace Brain/wiki articles.
  • `POST /api/v1/soul/wiki` recompiles the workspace wiki so external workflows can refresh insights on demand.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

GET /api/v1/brain/health

Health summary

Use this for dashboards, monitors, and reliability checks around the Brain compilation system.

GET /api/v1/soul/wiki

Query insights

Pull the current workspace's compiled articles and memory-like summaries.

POST /api/v1/soul/wiki

Refresh context

Trigger a recompile when your workflow needs fresh knowledge before automation or generation.

Agent-native customer ops

OpenClaw Self-Service

The Operator and Agency tiers unlock end-client onboarding via OpenClaw using signed portal magic links and fully scoped `end_client_mode: true` execution.

  • Enable the self-service tier for a workspace, then call `POST /api/v1/portal/invite` with a managed workspace and contact.
  • Share the returned `invite_url` with the client. The route issues a signed magic link and a scoped `portal_token`.
  • Pass that token into `POST /api/v1/portal/self-service` to keep every request client-scoped.

Why it matters

This section is designed for direct agent, Zapier, Make, and custom app integrations without losing SeldonFrame's premium UX or workspace isolation model.

POST /api/v1/portal/invite

Magic-link onboarding

Returns invite URL, portal token, expiry time, and onboarding metadata for end-client setup.

end_client_mode: true

Always scoped

Client actions are isolated to the invited workspace and contact context. No cross-client bleed.

OpenClaw cards

Premium UX

Return structured cards plus calm progress messages so mobile/agent flows feel deterministic and polished.