Skip to content

Authentication & The Operator Uplink

OPERATOR NOTE: The Aegis Matrix does not use traditional, static username/password gateways for API access. We bridge your verified Schrödinger's Market frontend session directly into our quantitative backend, generating a secure, dynamic Model Context Protocol (MCP) token for your autonomous AI agents.

Strategic Overview

Before your AI agent (whether it is Claude Desktop, Cursor, or a custom Python script) can access our options physics tools and Vault databases, it must prove its authorization.

The Aegis Matrix uses a secure key generation endpoint (/api/v1/auth/my-key) that translates your Ghost CMS member UUID into a unique aegis_ prefixed token. Once obtained, this token acts as your universal passport, passed via the X-API-Key header to establish a continuous Server-Sent Events (SSE) stream.

Step 1: Generating Your API Key

You do not need to generate your key manually. The Schrödinger's Market frontend handles the secure handshake for you.

The Operator Terminal Flow 1. Log In: Authenticate into your Schrödinger's Market Tier 02_Operator account. 2. Access the Terminal: Navigate to the Operator Terminal. 3. Decryption: The terminal's interface automatically retrieves your unique member UUID and fetches the API endpoint behind the scenes. 4. Copy the Key: If your account is authorized, the terminal will reveal a cyan bounding box with your aegis_ token. Click COPY to save it to your clipboard.

Under the Hood: The Generation Endpoint For developers building custom integrations, here is the exact mechanic the terminal uses to provision your key:

  • Endpoint: GET /api/v1/auth/my-key
  • Query Parameters:
    • uuid (string, required): The unique identifier assigned to your Ghost CMS member profile.

The Matrix Cryptography: When the backend receives your UUID, it passes it through a deterministic cryptographic hash, applying the aegis_ matrix prefix to generate your immutable clearance token. Raw UUIDs are never utilized in external payloads to ensure session integrity.

Success Response (200 OK): 

{
  "status": "authorized",
  "api_key": "aegis_1234567890abcdef"
}

Step 2: Connecting Your AI Agent

Once you have your aegis_ key, you must configure your AI agent to present it to the Aegis Matrix. The API utilizes a security governor that actively inspects every incoming request for the X-API-Key header.

If the header is missing, or if the key does not possess the correct matrix prefix, the connection is immediately severed and returns a 403 Forbidden error.

The SSE Lifeline

AI agents using the Model Context Protocol (MCP) do not make standard REST calls. Instead, they open a persistent, live lifeline to the Matrix called a Server-Sent Events (SSE) stream via the /sse endpoint.

To authorize this connection, your agent must pass the token in its HTTP headers.

Example cURL Request for testing the Uplink: 

curl -X GET "https://api.schrodingersmarket.com/sse" \
     -H "X-API-Key: aegis_your_copied_key_here"

Once the /sse connection is established and verified by the security governor, the agent will automatically discover our entire suite of quantitative tools (such as Merton probabilities and GEX nodes) and route its subsequent mathematical requests to the /messages endpoint.

Troubleshooting & Diagnostics

If you or your AI agent experience a [ FAULT ] Connection refused or ACCESS DENIED message, check the following:

  • Missing Header: Ensure your AI client is explicitly configured to pass the token under the exact header name X-API-Key.
  • Token Verification: Verify that you have copied the full token from the Operator Terminal, ensuring there are no trailing spaces and that the aegis_ prefix is intact.
  • System Health: If your keys are correct but the connection still fails, you can ping the public /health endpoint. If it returns {"status": "online"}, the backend is fully operational and the issue lies in your client's header configuration.