Open Platform
The Open Platform is DataGlass's organization console. Everything that belongs to your account rather than to a shop lives there: API keys, AI-assistant connectors, team seats, billing, and agency access. The workspace stays about selling; the Open Platform is about who and what can reach it.
It runs on its own site, open.dataglasslabs.com, and every page on it requires you to be signed in. There is no public or anonymous view.
How to open the Open Platform
- From the workspace, open the account menu (top-right) and pick Team or API keys — both jump straight into the Open Platform in a new tab.
- Or go to open.dataglasslabs.com directly. The session is shared with the app, so you arrive already signed in.
- Back to app in the sidebar returns you to the workspace.
What each Open Platform surface does
| Surface | What you do there |
|---|---|
| Overview | Your plan, member count and active-key count at a glance, plus shortcuts into the rest. |
| API keys | Issue and revoke personal access tokens for your own scripts and agents. |
| MCP connectors | Get the MCP server URL to paste into Claude or ChatGPT, and see where approved connectors are managed. |
| Team | Your organization, its members, their roles, and page-level access. |
| Billing & plans | Current plan and status, plan changes, and invoice history. |
| Agency access | Which outside agencies may work inside your organization. Owners only. |
| Agency | The client brands you may work in, if you are an agency operator. |
The last two only appear when they apply: Agency access to organization owners, and Agency only to an account that actually holds agency grants. An ordinary seller's sidebar shows neither.
API keys
A key is a personal access token starting with dg_pat_, issued to you for your own scripts and agents. It is shown once — DataGlass stores only a hash — so a lost token means revoking it and issuing a new one. Revoking is immediate, from the same page.
Full walkthrough and endpoint references: API getting started.
MCP connectors
The MCP page carries the server URL you paste into an AI assistant's connector settings, and the three steps of the flow:
- Copy the MCP server URL.
- In Claude or ChatGPT, open connector settings, add a custom connector, and paste the URL.
- You are sent to DataGlass to approve the connection, over OAuth 2.1.
Approved connectors appear alongside your API keys, and you revoke a connector's access there.
Step-by-step setup for each assistant: Connect Claude and Connect ChatGPT.
Team and roles
An organization is the tenant. Every user belongs to exactly one organization and holds one role in it — Owner, Admin, Manager, Member or Viewer. Any member can open Team and see the organization and its seats; owners add, invite and issue seats, change roles and status, remove people, and set page-level permissions.
The detail lives in Team and roles, Adding teammates and Managing access.
Billing
Billing leads with the current plan, its status (Active, Trial, Canceled or Past due) and its renewal or cancellation date, followed by the plan grid and your invoice history. Manage subscription hands off to the Stripe-hosted portal for payment methods and receipts.
Access is gated the same way the backend gates it: owners always have it, and other members need the billing page permission. Without it the page says billing is managed by your organization owner rather than showing a broken form.
Plans and prices: Pricing.
Agency access, from both sides
Agency work is two separate pages because it answers two different questions.
- Agency access (brand side) lists the outside firms allowed to work inside your organization. Every action behind it is owner-only.
- Agency (operator side) lists the client brands you may enter. Opening one mints a short-lived token against a seat inside that client's organization and reloads you into their workspace, where the app behaves exactly as it does for one of their own members. Leaving returns you to your own account.