Your shared
customer picture.
The POC now supports Supabase login, shared customer data, observations, audiences and plans. The anonymous demo remains separate.
Sign in and work together
- Choose Sign in and use your existing account’s email and password.
- Select a workspace you belong to, or create an empty workspace.
- Add customers or import CSV, record observations, explore Insights, and save audiences and plans.
- Use Reload shared workspace in settings to see newer team and source changes.
Owners can save. Readers can view, with email fields redacted. If another session saves first, your stale save is rejected: reload and reapply the change. Signing out returns to your local demo. Demo records are never automatically uploaded.
Connect existing systems
Base URL:
https://ikrborprotbvygphjphl.supabase.co/functions/v1/relasight
An operator provisions a workspace-scoped Relasight service token with explicit permissions and optional source restrictions. Store it in your warehouse job’s secret manager. Tokens expire within 90 days and can be revoked. The browser does not issue service tokens.
| Endpoint | Purpose |
|---|---|
| GET /health | Public service status |
| GET /v1/sources | List authorized sources |
| POST /v1/sources | Register a source |
| POST /v1/ingestion/batches | Import versioned customers and observations |
| GET /v1/ingestion/batches/{id} | Read a batch result |
| POST /v1/identity-links | Link customer identities across sources |
| GET /v1/customers?q=&limit=25 | Search authorized customer profiles |
| GET /v1/customers/{id} | Read customer evidence |
| POST /v1/insights | Run renewals, expansion, concerns, themes or quality analysis |
| POST /mcp | Read-only MCP tools for an authorized AI client |
Use Authorization: Bearer <service-token>. Source creation, ingestion and identity linking also require an Idempotency-Key. API ingestion is synchronous: a successful batch returns HTTP 200 with per-item results. Check every result before advancing your sync watermark.
The proposed integration contract includes payload examples and warehouse sync patterns. Its production features exceed this deployed POC: pagination, asynchronous 202 jobs, configured source priority and managed connectors are not implemented. Current source lists are unpaginated, request bodies are limited to 1 MB, batches accept up to 500 items, and evidence resolves at day precision.
One layer for data and insights
Imported profiles and observations appear read-only in the workspace. Correct them in the source system and resend a higher version. You can add manual observations to an imported customer. Manual customer records and observations also appear in authorized REST and MCP queries.
Cross-source linking currently covers imported identities. Linking a manual customer to a source identity is not yet available. Email redaction does not remove personal data embedded in names or observation text. AI processing is not automatic; the POC’s Insights screen uses explicit calculations.
Browser workspace endpoints
These routes require a verified Supabase user access token, not a service token. GET /v1/workspaces lists memberships. POST /v1/workspaces accepts a name and UUID request_id to create an empty workspace; each account can own up to three.
GET /v1/workspace loads data and revision; POST /v1/workspace saves a validated document and expected revision. Both require X-Relasight-Workspace. Only owners may save. HTTP 409 means the workspace changed and must be reloaded. For automated source imports, use the ingestion API instead of replacing workspace documents.