The revenue stack, as an API
Free test keys. Sandbox included. No credit card.
By signing up you agree to graph8's Terms and Privacy Policy.
import { g8 } from "@graph8/sdk" const buyers = await g8.contacts.search( { title: "VP Sales", intent: "high" })await g8.sequences.enroll(buyers, "launch")await g8.meetings.autobook()Buyers found, enriched
Meeting booked
Thu 10:30, Ava Bello
booked by your app
What is a graph8 primitive?
A preview-ready GTM capability exposed as an API, UI component, MCP action, or workflow step. Compose them instead of rebuilding the infrastructure.
Data
Engagement
Workflow
AI
Observability
Composable by default
A complete revenue app runs on these primitives, the same ones graph8 uses for approved workspaces.
Dashboard
Last 30 days
Pipeline created
$2.4M
+18%
Meetings booked
38
+6
Reply rate
24%
+3pts
Active sequences
12
live
Pipeline created
$2,412,900
A complete revenue app on these primitives.
You own the product. graph8 runs the infrastructure.
Your app controls the workflow, UI, business logic, and customer experience. graph8 handles the primitives underneath: data, enrichment, sequencing, inbox, meetings, routing, observability, and agent execution.
Skip the infrastructure. Keep the upside.
Start from graph8's own revenue primitives with a sandbox first, then request production access when your workspace is approved.
01
Preview the whole backend
Revenue backend, CDP, warehouse, enrichment, dialer, email, and engage surfaces are yours to preview before you commit to building that layer yourself.
02
Zero ops to maintain
graph8 runs upgrades, scaling, security patching, deliverability, provider integrations, and data refreshes for approved workspaces. You ship product, not pipelines.
03
Production-grade primitives
Start from the same multi-tenant primitives graph8 uses internally, with audit logs, scoped keys, and rate limits documented before production access.
Your app connects once. graph8 talks to everything else.
One integration. graph8 reaches email, CRM, calendar, data, the web, and your agents, and keeps them in sync.
Four ways to build. Pick yours.
SDK for your app, REST for your backend, MCP for your agents, CLI for your terminal. Same primitives, same key, pick by how you build.
| I'm building... | Use | Why |
|---|---|---|
| A browser app (React, Next.js, Vue) | JavaScript SDK | Typed, SSR-safe, React hooks, widgets |
| A server script or backend | REST API or CLI | Direct HTTP or terminal commands |
| AI-powered workflows | MCP Server | 43 tools, natural language |
| A quick prototype | CLI | Fastest to test, JSON output |
From the developer docs: Which should I use?
Each component is pre-wired to the graph8 SDK and reads sandbox data first. Move to an approved workspace when production access is granted.
Browse every surface as components$ npm install @graph8/contact-card$ npm install @graph8/sequence-builder$ npm install @graph8/calendar$ npm install @graph8/agent-chatA campaign, from create to launch.
Four calls take a campaign from empty to a review-ready sandbox run, on the same primitives that power graph8.
const run = await graph8.campaigns.create();
// spin up a campaignawait run.addAudience();
// pull the matching buyersawait run.generate();
// draft every step with AIawait run.launch();
// request reviewBuilt for sandbox first, then review.
Build with test keys, inspect logs and usage, then request production workspace access when the integration and terms are ready.
Preview
Access stage
Scoped
API keys
OAuth
and SSO
Rotatable
keys, per route
Rate limits
per key, per route
Multi-tenant
isolated by org
Audit logs
every action
Review
production access
Get your sandbox key and test today.
Start in preview. Production access is approved workspace by workspace.
Start with one primitive. Grow into the full GTM runtime.
Call one primitive today and grow into the whole stack on the same backend. No migration, no infrastructure to run.