Developers & AI agents

Public API & automated discovery

What automated systems can discover and call on FounderPulse, and what stays private.

1. Scope

FounderPulse is a web application. Product data (goals, daily actions, measured outcomes, AI Co-Founder conversations) is strictly private and reachable only by the authenticated user inside the app.

The public HTTP surface is intentionally minimal: one availability endpoint and signed machine-to-machine callbacks. No public endpoint returns personal data.

2. Automated discovery

  • API catalog (RFC 9727): /.well-known/api-catalog: application/linkset+json
  • OpenAPI 3.1 description: /api/public/openapi.json
  • Documentation: /api-docs (this page)
  • Health: /api/public/health

3. Endpoints

  • GET /api/public/health: returns { "status": "ok", "service", "time" }. Open, no authentication.
  • POST /api/public/payments/webhook: payment provider callback. Signature required, replays rejected.
  • POST /api/public/resend/events: email delivery events (bounces, complaints, unsubscribes). Signature required.

Webhook endpoints are not meant for third-party clients: unsigned requests are rejected.

4. Usage, limits and contact

Automated agents may read this documentation, the OpenAPI description and the health endpoint. Please keep a reasonable rate (a few requests per minute) and send an identifiable User-Agent.

For application access or an integration, use the contact page.

RFC 9727 compliant (API catalog). Last updated: August 2026.

← Back to site