What You Get In The Portal
- entitlement-aware access to the Sports MCP Server product page
- self-serve API key management
- operational visibility into usage and recent activity
- commercial controls for alerts, extra usage, billing, and exports
- user and role management for the customer organization
The Main Portal Areas
| Area | Why it matters |
|---|---|
Products -> Sports MCP Server -> Overview | quick orientation and launch path |
Products -> Sports MCP Server -> Usage | operational usage, key breakdowns, recent calls, and server health signals |
Products -> Sports MCP Server -> API | keys and CORS Origins |
Products -> Sports MCP Server -> Settings | Usage Notifications and Extra Usage |
Settings -> Billing | current period and billing history |
Settings -> Exports | org-wide usage exports |
Settings -> Users | invites, role changes, and access revocation |
Settings -> Legal | legal documents |
Roles
| Action | Member | Admin | Owner |
|---|---|---|---|
| View product overview and usage | Yes | Yes | Yes |
| Create or delete API keys | No | Yes | Yes |
| Add or remove CORS origins | No | Yes | Yes |
| Configure usage notifications | No | Yes | Yes |
| Enable or disable extra usage | No | Yes | Yes |
| Export usage data | No | Yes | Yes |
| Invite or manage users | No | Yes | Yes |
Recommended Rollout Sequence
- Confirm the organization has the right entitlement for Sports MCP Server.
- Decide who will be the operational owner inside the portal.
- Create environment-specific API keys.
- Configure notifications and extra-usage policy before launch.
- Make sure finance or operations knows where exports and billing live.
Why This Matters During Evaluation
Buyers and builders usually evaluate together. The portal reduces friction in both tracks:- builders get keys and technical controls without waiting for manual provisioning
- operators and finance teams can see usage, billing, and governance in the same product story
Common Mistakes
- treating the portal as an admin-only appendix instead of part of the rollout
- waiting until after launch to configure usage notifications
- keeping ownership implicit, so no one watches billing or exports
- creating keys before the team agrees on environment naming and responsibility