Overview

OpenPoly Mini App lets an operator embed Opinion market trading and shared Polyflight rounds while keeping operator-owned wallet balances and webhook receivers.

Operator responsibilities

• Call POST /api/operator/launch from your backend
• Implement wallet adapter paths such as GET /balance and POST /debit
• Receive signed webhook events
• Configure API keys, callback endpoints, Opinion visibility, and Polyflight reporting access in operator dashboard
• Run staging drills before production launch

OpenPoly responsibilities

• Mini App UI for Opinion and Polyflight
• Operator API surface
• Product-specific quote/execution and shared-flight proof
• Opinion settlement plus dedicated Polyflight native-IDR statements/liabilities
• Signed webhook delivery
• Operator dashboard

Environment model

Staging and production use the same source code, same URL paths, and same integration rules.

Only base URL values and environment configuration differ.

Next steps

• Integration checklist
• Architecture
• Operator API authentication
• Polyflight overview and launch