35 typed entities across 9 domains — one graph

The Operating System for Agent-First Startups

Nine domains, 35 typed entities, one graph. Your AI agent runs CRM, billing, support, projects, marketing, analytics, and more — autonomously.

agent.ts

import { $ } from '@headlessly/sdk'

$.Deal.closed(async (deal, $) => {
  await $.Subscription.create({ plan: 'pro', customer: deal.contact })
  await $.Campaign.create({ name: `Onboard ${deal.name}`, type: 'Email' })
  await $.Ticket.create({ subject: `Welcome ${deal.name}`, requester: deal.contact })
})

One SDK Replaces Your Entire Stack

Stop stitching together 15 API keys, 15 webhook endpoints, and hundreds of lines of glue code.

Typed Entities

Business Domains

MCP Tools

SDK

One Graph. Zero Glue.

Your agent spends more time on glue code than on the work that matters. There's a better architecture.

The Old Way: Integration Hell
With headless.ly: One Typed Graph

The Old Way: Integration Hell

# The old way: 15 API keys
STRIPE_KEY=sk_live_...
HUBSPOT_KEY=pat-na1-...
SENDGRID_KEY=SG.abc123...
ZENDESK_KEY=zd_...
MIXPANEL_TOKEN=mp_...

// 15 webhook endpoints, 15 auth flows
app.post('/webhooks/stripe', handleStripe)
app.post('/webhooks/hubspot', handleHubspot)
app.post('/webhooks/zendesk', handleZendesk)
app.post('/webhooks/sendgrid', handleSendgrid)

With headless.ly: One Typed Graph

import { $ } from '@headlessly/sdk'

// Every domain. One import.
$.Deal.closed(async (deal, $) => {
  await $.Subscription.create({
    plan: 'pro',
    customer: deal.contact,
  })
  await $.Campaign.create({
    name: `Onboard ${deal.name}`,
    type: 'Email',
  })
  await $.Ticket.create({
    subject: `Welcome ${deal.name}`,
    requester: deal.contact,
  })
})

Contact.ts

import { Noun } from 'digital-objects'

export const Contact = Noun('Contact', {
  name: 'string!',
  email: 'string?#',
  stage: 'Lead | Qualified | Customer | Churned | Partner',
  company: '-> Company.contacts',
  deals: '<- Deal.contact[]',
  qualify:  'Qualified',
  capture:  'Captured',
  assign:   'Assigned',
})

Frequently Asked Questions

headless.ly unifies CRM, billing, projects, content, support, analytics, marketing, experiments, and platform automation into one typed graph of 35 entities. Instead of 15 API keys, 15 webhook endpoints, and hundreds of lines of glue code, you get one SDK import: import { $ } from '@headlessly/sdk'.

search finds entities by type and filter, fetch retrieves entities with related data via graph traversal, and do executes typed operations. One MCP server gives your agent full access to all 9 domains — CRM, billing, support, projects, marketing, analytics, experiments, workflows, and content.

Every verb — built-in CRUD and custom verbs like qualify() — has three lifecycle hooks: qualifying() (before, for validation), qualify() (execute), and qualified() (after, for cross-domain reactions). The callback receives the entity and a $ context for triggering operations across the entire graph. No webhooks to configure.

Entities are defined with Noun() from digital-objects — a zero-dependency, zero-codegen schema language. One declaration defines fields, enums, relationships (->, <-), custom verbs, and state machines. Full TypeScript inference means your IDE knows every field and verb at compile time.

Both. The typed graph and verb lifecycle work identically whether called by a developer writing TypeScript or an AI agent using MCP tools. The difference is that headless.ly was designed agent-first: three tools instead of three hundred endpoints, typed operations instead of form submissions, and graph traversal instead of manual data joins.

Create an Org. Get Everything.

CRM, billing, support, projects, marketing, analytics, experiments, and platform automation — one install.

35 Entities
9 Domains
3 MCP Tools

Get Started