PONSSetup & operations
The services and configuration required to activate builds and funding.
Web application
The default Next.js website runs on Vercel, with public research pages available without secrets or storage. Saved requests, votes, accounting and build activity require persistent storage and the trusted account gateway. The optional Cloudflare runtime supports D1; the current Node/Vercel runtime still needs a durable database adapter. A browser-supplied wallet address is not account authorization.
FORKD_AUTH_GATEWAY_SECRET # trusted account gateway
GITHUB_TOKEN # optional source API credential
BUILD_RUNNER_URL # HTTPS runner /jobs endpoint
BUILD_RUNNER_SECRET # shared service authentication
BUILD_MODEL_LABEL # selected public model label
ROBINHOOD_RPC_URL # read-only chain verification
OPERATOR_API_SECRET # funding settlement authority
FORKD_PUBLIC_REPOSITORY # public owner/repository
FORKD_TOKEN_ADDRESS # actual deployed main token
FORKD_TREASURY_ADDRESS # actual treasury address
FORKD_ROUTERS # request UUID to verified router JSONRunner service
Deploy the separate Node runner with durable job storage and a prepared E2B template. Connect a funded model account, specify the model and current conservative cost ceilings, and configure authenticated access for callbacks. Never expose service credentials through browser configuration.
OPENROUTER_API_KEY
OPENROUTER_MODEL
E2B_API_KEY
E2B_TEMPLATE
FORKD_APP_ORIGIN
RUNNER_PUBLIC_ORIGIN
RUNNER_DB_PATH
MODEL_MAX_USD_PER_MILLION
SANDBOX_USD_PER_SECONDFee routers
Deploy a reviewed router per request with its immutable request key, build treasury, main treasury and verified PONS fee escrow. Register the address only after checking chain, bytecode and constructor values. Test the entire claim, transfer, receipt and settlement flow before funding it.
Before opening public access
- Identify the responsible operator and provide a working support and legal-notice channel.
- Review the terms and privacy notices for the actual service, audience and jurisdiction.
- Connect and verify paid services and review treasury controls.
- Define review authority, deployment signing, failed-job reconciliation and incident handling.
- Verify production identity, per-account limits, request retention and service authentication.
Detailed configuration and recovery
The configuration reference explains which environment belongs to each service. Use the lifecycle and troubleshooting guides when an accepted job is interrupted or a callback cannot be delivered.