OlyBench
Oly Platform
Email verification
Verify your email
Verification links are safe and non-enumerating in the UI. Raw token values are never printed or copied into hidden fields.
First-run setup
The next action stays inside the canonical OlyBench app and waits for backend identity, tenant, and capability checks.
Check your email
Account creation starts in pending_email. Product reading is allowed, but buying, inviting, job creation, and product MCP stay blocked.
Verification required before protected actions
These controls are intentionally blocked in the UI contract and must also fail closed on the backend.
Buy or start checkout
Email verification must complete before checkout can be configured or started.
Blocks /api/checkout/sessions with billing.checkout.create
Invite teammates
Team invitations require a verified identity plus an owner or admin role in a validated workspace.
Blocks /app/workspaces/{workspace_id}/team/invitations with members.invite
Run reports or tools
Job submission requires verified identity, workspace scope, input validation, readiness, and entitlement checks.
Blocks /api/workspaces/{workspace_id}/jobs with jobs.create
Access product MCP
Product MCP requires the gateway to verify identity, capability, rate limits, and audit context.
Blocks MCP gateway with mcp.product.access