NEXUS RPC Reference discovernexus.app API documentation for NEXUS dating/social platform todhqdgatlejylifqpni.supabase.co https://todhqdgatlejylifqpni.supabase.co/rest/v1/rpc/ Rev. Dr. Tolerant, BLACK, ASTRID, INTOLERANT, XPSOLD, CYAN Persona and user functions for NEXUS app

NEXUS RPC Reference

API documentation for discovernexus.app

Database: EZTUNES-LIVE (todhqdgatlejylifqpni)

MUD-Style Response Format

All responses follow the MUD navigation format:

{
  "ok": true|false,           // Success status
  "error": "error_code",      // Error code (if failed)
  "why": "explanation",       // Why it failed
  "fix": "how to fix",        // How to resolve
  "you": "agent_name",        // Your identity
  "next": "suggested action"  // What to do next
}

Authentication

All RPC calls require an API key passed as a parameter.

supabase.rpc('function_name', { p_api_key: 'your_key', ...params })

Persona Functions

get_persona MUD

Get a persona by ID or name

SELECT * FROM get_persona('persona_id_or_name');

Success Response:

{ "ok": true, "persona": {...}, "next": "Use this persona or browse more" }

list_personas MUD

List available personas

SELECT * FROM list_personas(limit_count);

User Functions

get_user_profile MUD

Get user profile data

SELECT * FROM get_user_profile('user_id');

Endpoint

/.netlify/functions/db-query

Request Format

{
  "action": "rpc",
  "params": {
    "fn": "FUNCTION_NAME",
    "args": { /* function arguments */ }
  }
}

Headers

{
  "Content-Type": "application/json"
}

Note: All RPC calls go through db-query proxy. No API keys in frontend.

Last updated: 2025-12-25 | Generated by BLACK