docs · developers
Build on top of Pulse.
The knowledge graph, ingestion, and MCP surface as real developer APIs. Read the graph over GraphQL, push documents from systems without a native connector, or wire your AI client in so “save this to Pulse” works from inside Claude Desktop, Cursor, or Codex CLI.
api· 3
- REST API v1 referencePlain JSON over HTTP for the same map graph, briefings, skills, and answer surface the MCP server exposes, in a flatter shape. Bearer tokens with scopes, rate-limited, /api/v1/* endpoints.
- GraphQL knowledge-graph APIQuery decisions, features, commitments, topics, people, customers, and disagreements over a single read-only endpoint. Bearer auth with API keys from /app/admin/api-keys.
- Push API for custom ingestionPOST documents from systems Pulse doesn't have a native connector for. Idempotency keys, structured metadata, ACL row creation. Flows through the same 6-event extractor pipeline as connector data.
mcp · ai clients· 3
- MCP server overviewThe Model Context Protocol server behind the capture tools. Map, briefings, skills, and answer tools over JSON-RPC for any MCP-aware client. Read by default, per-call permission checks, audited.
- Capture conversations from AI clientsSeven MCP capture tools (pulse_capture_conversation, _snippet, _decision, _commitment, _failure_case, _note, plus pulse_suggest_skill) let Claude Desktop, Cursor, and Codex CLI push AI conversations into your workspace. Per-user pulse_mcp_* tokens, demo-blocked.
- Personal memory across AI toolsCarry your own private facts and writing/coding style across AI tools. pulse_remember / pulse_recall / pulse_forget, scoped to you, recalled in any client. Private to you, never team-visible; opt-in auto-capture + style learning; audited break-glass.
capture · connectors · modeling· 3
- Drop-anywhere captureCapture a thought or file without opening the app: POST /api/v1/capture from an iOS Shortcut / Share Sheet, or drop a file in the ~/.pulse/inbox/ watched folder. Per-user token, lands private to you (AUTHOR_ONLY) in the Captured inbox.
- Codebase indexingConnected GitHub and GitLab accounts index source code itself, not just PRs and issues. Tree-API walk, secrets deny-list (.env, keys, node_modules, binaries, >100KB), 5,000 files per repo, ACL mirrored from repo collaborators.
- Custom entity typesModel your own domain: define entity kinds (Vendor, Incident, Experiment) with custom fields and optional per-type extraction. Admin-defined workspace types or private personal types. They get compiled-truth pages and surface in Map and Ask.
api auth
All of these surfaces use Bearer tokens minted at /app/admin/api-keys (workspace keys, OWNER-only) or /app/settings/integrations/mcp-tokens (per-user MCP capture tokens, MEMBER+). Tenant-scoped, rate-limited, demo-blocked on write paths.