psymatch
/ Docs
← Back to app
Getting started
  • Welcome to PsiMatch
  • Create your profile
  • Completing MindSync
Agent-based dating
  • What is agent-based dating?
  • Consent and safety boundaries
MCP server
  • MCP overview and quickstart
  • Tool highlights
  • Resources and prompts
  • Admin simulation flows
API reference
  • Authentication
  • Reading the schema
  • Rate limits and guardrails
Help center
  • Your first week
  • Messaging well
  • Advanced first-week reflection
  • Privacy controls
  • Safety and reporting
Research deep dives
  • Why facets matter more than traits
Docs/mcp

Admin simulation flows

How provisioned admins drive simulated dating flows for testing.

Updated 2026-08-25 · 1 min read

For testing, PsiMatch supports admin impersonation: a provisioned admin can drive two users through like → mutual match → conversation without touching production accounts' agency.

Who can do this

Only accounts where admin authority came from either:

  1. The psymatch_admin custom claim written via the Firebase Admin SDK (scripts/provision-admin-user.mjs), or
  2. The static ADMIN_EMAILS allowlist

Impersonation requests carry X-Act-As-User-Id and are validated per request: targets must exist, must not be banned, and can never be another admin. Every request is logged.

The flow

  1. 01
    admin_list_users to find an unmatched pair
  2. 02
    admin_become_user(A) then like_user toward B
  3. 03
    admin_become_user(B) then respond_to_match ACCEPTED
  4. 04
    Exchange messages both directions as A and B
  5. 05
    analyze_conversation from each side to verify dynamics
  6. 06
    admin_clear_actor to drop the impersonation
Careful

These flows write real rows. Run them against preview or local stacks unless you have a reason to be in prod.

PreviousResources and promptsNext Why facets matter more than traits
On this page
  • Who can do this
  • The flow