Environments | Phoenix Prediction Docs

Phoenix supports multiple operator environments. Most operators use at least:

Environment	JWT `env` value	Use for
Sandbox	`sandbox`	Integration testing, iframe review, wallet operation testing, and admin training
Production	`prod`	Real players, real content, real wallet behavior, and production reporting

Environment selection is part of the launch token. Phoenix reads the operator code from iss and the environment from env, then loads the matching operator environment.

Keep environments separate

Sandbox and production can have different signing keys, wallet base URLs, allowed parent origins, supported currencies, listings, market settings, and settlement workflows.

Environment-Scoped Values

Confirm these values for each environment before launch:

Value	Why it is environment-scoped
Ed25519 public key	Phoenix verifies tokens and signed requests against the matching environment
Allowed parent origins	Sandbox should allow staging/test hosts; production should allow only production hosts
Wallet base URL	Sandbox should call a test wallet; production should call the real wallet
Supported currencies	Sandbox can test currencies before production rollout
Listings and market settings	Listing placement and market configuration can be tested before they affect production players
Wallet operation contract	Currency scales, signatures, idempotency, and status lookup must be confirmed per environment

Using a production player with a sandbox token is a launch bug. Using a sandbox wallet URL from production is a finance risk.

Phoenix provides exact hostnames for each operator environment during onboarding. Use the hostnames assigned to your environment in production code and monitoring.

Backend Host

https://prediction.phoenixverse.io

Public paths:

Path	Purpose
`/health`	Liveness probe (returns literal body `ok`, unauthenticated)
`/openapi.json`	Operator API OpenAPI spec
`/docs`	Redoc UI (OpenAPI)
`/.well-known/signing-key.pem`	Phoenix Prediction platform public key for wallet operation verification
`/operator/api/*`	Signed Operator API
`/embed/api/config`	Public iframe boot configuration when the operator is supplied by token only
`/o/{operator_code}/embed/api/config`	Public iframe boot configuration with path-level operator check

Token Examples

{
  "iss": "acme",
  "env": "sandbox",
  "typ": "visitor",
  "aud": "pmm_default",
  "exp": 1779100900
}

{
  "iss": "acme",
  "env": "prod",
  "typ": "visitor",
  "aud": "pmm_default",
  "exp": 1779100900
}

Embed URL Shape

The embed URL follows this shape:

https://embed.prediction.phoenixverse.io/o/{operator_code}?token={JWT}

Use the embed host assigned to your environment.

If the path operator and token operator do not match, Phoenix rejects the launch.

Wallet Operation Testing

Phoenix must be able to reach the wallet base URL from its own environment. An operator laptop localhost URL is not reachable from Phoenix-hosted sandbox or production services.

Use one of these approaches for wallet operation testing:

Deploy a sandbox wallet endpoint on an HTTPS host that Phoenix can reach.
Use a temporary HTTPS tunnel that forwards to a local wallet service during development.
Run Phoenix and the wallet service in the same local development stack when Phoenix provides that setup.

Do not configure shared sandbox or production environments with localhost wallet base URLs.