Pulse / Developer Platform

Everything Pulse can do, your product can call.

Use the same contracts behind first-party Pulse surfaces: APIs, SDKs, OAuth, webhooks, MCP, files, agents, workflows, context, events, and traces. Connect a system, embed an experience, publish a capability, or build something entirely new.

Join the waitlist Explore the platform

REST APIsSDKsOAuthWebhooks

DEVELOPER / CAPABILITY PLAYGROUNDSANDBOX · US-WEST

POST/v1/agents/runs

{
  "agent": "revenue-watchtower",
  "input": {
    "account_id": "acct_4821",
    "objective": "prepare recovery plan"
  },
  "require_approval": true
}

201 CREATEDRun accepted184 ms

run_01JQ8Y · trace available · approval pending

TypeScript Python REST WebhooksSame primitives as Pulse

What makes a real platform

An API around a chat box is not a platform.

Developers need the same primitives the product itself trusts: identity, data, files, agents, workflows, events, permissions, traces, and operating limits. Pulse exposes the actual capability fabric.

01 / PARITY

Build with first-party primitives.

The same contracts behind Pulse surfaces are available through APIs, SDKs, webhooks, MCP, OAuth, and embeddable experiences.

02 / CONTEXT

Integrations join the architecture.

External tools can participate in identity, permissions, events, traces, and shared context instead of sitting behind a brittle bridge.

03 / OPERATIONS

The integration is observable from day one.

Inspect usage, versions, limits, failures, latency, tool calls, agent runs, and downstream outcomes.

The open edge

Everything Pulse can do, your product can call.

Connect your system, embed a surface, publish a capability, or build an entirely new experience on the shared Pulse architecture.

01REST APIs

Call stable contracts for data, files, agents, workflows, work, and events.

02SDKs

Use typed client libraries and helpers in the languages your team already ships.

03OAuth

Authorize users and organizations through explicit, reviewable scopes.

04Webhooks

React to durable events with signatures, retries, logs, and delivery state.

05MCP

Publish governed tools that agents can discover and invoke safely.

06Capabilities

Package reusable actions and product primitives for Pulse experiences.

07Playground

Test requests, inspect responses, stream events, and explore contracts live.

08Usage + limits

Operate keys, quotas, spend, latency, errors, versions, and environment boundaries.

From a script to an ecosystem

Open enough for a weekend build. Governed enough for a product platform.

Start with one call, then expand into connected tools, embedded experiences, published capabilities, and customer-facing products.

01BUILDERS

Prototype against the real system.

Use the playground, SDKs, webhooks, and APIs to move from idea to working integration quickly.

02PRODUCT TEAMS

Put Pulse capability inside your experience.

Embed intelligence, agents, files, workflows, context, and actions without cloning the platform.

03PLATFORMS

Extend the ecosystem with clear contracts.

Publish tools and capabilities with scopes, versions, observability, limits, and operational ownership.

THE OPERATING ARCAUTH → CALL → EVENT → TRACE → OPERATE

1Choose the capabilityData, files, agents, actions, events, identity, or embedded experience.2Build against a clear contractAPI, SDK, OAuth scope, MCP tool, webhook, and test environment.3Ship with operational contextObserve usage, limits, failures, versions, and the outcomes created.

An extensible platform with a coherent product on top.

The extension feels native because it runs on the same contracts as Pulse itself.

Join the waitlist See packaging