Sign in

Partner API

Give your community the same peer-support sitter we run on trip-sitter.AI — through a simple, server-to-server API built for festivals, peer groups, and care-adjacent apps.

What it is

The Partner Sitter API is a hosted harm-reduction chat service. Your backend sends conversation turns; we stream replies using our curated trip-sitting standard operating procedures, red-flag triage, and grounding techniques. You keep your own UI and user relationship — we provide consistent, non-directive peer support at scale.

Who it is for

  • Events & nightlife

    Festivals, raves, and harm-reduction teams that want 24/7 sitter access inside a web app, kiosk, or staff tool.

  • Community organizations

    Peer-led groups that need a trusted first line of support when volunteers are offline.

  • Product partners

    Apps building wellness or integration features who should not run their own clinical-style bots or expose model keys.

What you get

  • Same sitter as trip-sitter.AI

    English and Traditional Chinese, aligned with our public peer chat — not a generic chatbot.

  • Crisis-aware responses

    Hard red-flag phrases trigger an immediate emergency-oriented response and stop open-ended coaching.

  • Secure access

    Organization-scoped API keys (Bearer tokens), revocable at any time, with monthly usage caps.

  • Privacy by default

    The API does not store conversation content on our side; you control retention in your product.

What it is not

This is peer support and education — not medical care, psychiatry, therapy, or emergency dispatch. Partners must show users clear scope language before chat starts and must not market the service as a doctor, therapist, or crisis hotline replacement. In acute medical or self-harm emergencies, users need local emergency services.

How access works

We onboard partners manually after screening: we issue a live API key, agree on monthly message limits, and share integration details. Your servers call our chat endpoint over HTTPS with the key in the Authorization header. Usage for the current UTC month is returned in response headers so you can monitor caps.

Current endpoint (v1)

POST /api/v1/sitter/chat

Request access

Tell us about your organization, expected volume, and how users will see disclaimers. We will follow up with pilot terms and technical onboarding.

Contact us

Detailed integration docs (request schema, SSE format, error codes) are provided after partnership approval.