Status
Real-time component-level status will move to a dedicated status surface; this page reflects the platform's steady-state operational posture.
Components
Inbound MX
mx1.primitive.dev, mail intake + parsing
Outbound relay
API send pipeline, DKIM signing, deliverability
API
api.primitive.dev/v1, bearer-authenticated REST surface
OAuth
/oauth/* surface, RFC 8414 / RFC 9728 metadata, dynamic client registration
Dashboard
web app at www.primitive.dev, signed-in user surface
Hosted Functions
JavaScript handlers invoked on every inbound email
Webhook delivery
Outbound webhook dispatch with retry queue
For agents
This page is for human readers. Agents that need to gate on platform availability should probe https://api.primitive.dev/v1/whoami with a valid bearer token. A 2xx response indicates the API path is reachable; a 5xx persisting across retries indicates a real outage. The Primitive API also returns Retry-After on 429 responses, which agents should honor.
Reporting an outage
If a Primitive surface appears down to you but this page says otherwise, please email contact@corp.primitive.dev with the affected endpoint, timestamps, and any request IDs from response bodies (the API includes request_id on every error envelope).