WePeopleDocs
IntegrationsPricingDocsSign inGet started
Get started
Docs home

Getting Started

  • What is WePeople
  • First week checklist
  • Core concepts

Product

  • Monitoring
  • Reports
  • People & profiles
  • SPACE scoring
  • Organization settings
  • Statistics
  • Billing & retention
  • Privacy model

Integrations

  • Overview
  • Slack
  • GitHub
  • Jira
  • Trust model

Developers

  • Platform overview
  • Quick start
  • Ingest guide
  • Custom statistics
  • Hosted MCP
  • TypeScript SDK

API Reference

  • Overview
  • Auth & headers
  • GET ping
  • POST events
  • POST snapshots
  • Apps statistics
  • Error codes
  • OpenAPI & SDK

Browse docs

Developers

Developer platform

Stream CRM tickets, CI deploys, AI agent activity, and internal-tool signals into the same monitoring timeline your team already reads — or pull panel data back out for AI clients. Everything is scoped to your organization; keys and tokens never cross tenants.

Overview

The developer platform has two complementary surfaces:

  • Ingest API — push discrete events and point-in-time snapshots with wp_live_* API keys.
  • Hosted MCP — read people, monitoring, scores, and statistic rollups with membership-linked wp_mcp_* tokens at https://wepeople.app/api/mcp.

Base URL for REST: https://wepeople.app. Create apps and keys under Organization → Developer.

Smoke-test a keybash
curl "https://wepeople.app/api/v1/ingest/ping" \
  -H "Authorization: Bearer $WEPEOPLE_API_KEY"

Push vs read

Ingest is write-only: your services call REST endpoints to land data on the monitoring timeline and user strip. Data appears as custom:<app-slug> alongside Slack, GitHub, and Jira.

MCP is read-only: Cursor, Claude, or other MCP clients query the same panel surfaces the product UI uses — with RBAC scopes on each tool. There are no write tools in v1.

Private per organization

API keys belong to one developer app in one org. MCP tokens are tied to a membership in that org. Neither surface exposes data across tenants.

Events & snapshots

Events are discrete things that happened — ticket resolved, deploy shipped, doc merged. Batch up to 100 per request; partial failures return 207 Multi-Status so you retry only rejected rows.

Snapshotsare “right now” gauges — open ticket count, queue depth, SLA attainment. Only the latest snapshot per (worker, snapshotType) renders on the user strip.

Register custom statistics so your event types feed reports and rollups with explicit aggregation rules.

Choose your path

Quick startCreate an app, issue a key, send your first event in minutes.Ingest guideAuth, workers, events, snapshots, idempotency, limits, and security.Custom statisticsDeclare statistic manifests your events feed into rollups.Hosted MCPConnect AI clients to read monitoring panel data.TypeScript SDKInstall @wepeople/sdk for typed clients with retries.API referenceEndpoint-by-endpoint contracts, field tables, and error codes.

Machine-readable contract: /openapi/v1.yaml and sdk-typescript.

On this page

  • Overview
  • Push vs read
  • Events & snapshots
  • Choose your path
WePeople

Team insight, not surveillance. A lead's-eye view built on metadata from the tools your team already uses — never source code, never messages, never DMs.

Product

  • Monitoring & Reports
  • SPACE scoring
  • Pricing

Docs

  • Docs home
  • Getting started
  • Developer platform
  • API reference
  • MCP

Integrations

  • Browse integrations

Company

  • Support
  • Status

Legal

  • Brand
  • Privacy
  • Terms

© 2026 WePeople. Built with care.

Metadata only. No source code, no message bodies, no DMs — read the policy.