Today, we are killing seat-based pricing to let you provide secure, authenticated access to your thousands of users, clients or employees.
Our customers spoke: They want to give thousands of people secure access to their CustomGPT.ai agents, without paying for each seat (like ChatGPT or Claude).
Now, you can use your existing identity provider to connect directly to your CustomGPT.ai agents. Users authenticate the way they always do – through Google Workspace, Microsoft Entra ID, Okta, PingOne, or any SAML 2.0 provider – and land on the right agents automatically.
No accounts to create. No passwords to manage. No admin overhead as people join or leave. Sessions last 24 hours and no user is ever stored in CustomGPT.ai.
Now, you can give every employee / student / client secure access to your AI agents, without buying seats or provisioning accounts.
Example Scenario: 7,000 person University
Instead of paying per seat, this university can now enable custom GPTs with their institutional knowledge and make it securely accessible (using their own login system) to all their students and faculty.
No more buying 7,000 licenses of Microsoft Copilot, just to create secure custom agents.
Set it up once
Your IT team connects your IdP, maps user groups to agents, and picks a deployment method – either a single portal link that routes everyone to the right place, or an embedded agent on your website or intranet.
Your IdP handles who gets in (See setup guide).
Great fit for Enterprise like:
- Consulting firms give clients secure access to project agents through the client’s own corporate login.
- Universities connect campus SSO so students access course-specific agents based on class enrollment.
- Manufacturing companies route partners to the right product documentation based on their partnership tier.
The pattern is the same: the users already exist in your identity system. Now that system controls their AI access too.
Available Now
This is an Enterprise feature that needs to be enabled on your account. Reach out and we’ll get you set up.
Frequently Asked Questions
Do I need a paid seat for every employee, student, or client who uses an AI agent?
No. GEMA handles 248,000 member inquiries a year with an 88% success rate, which shows why seat-based access breaks down at scale. IdP-based end-user access lets employees, students, clients, or partners sign into specific agents through your existing identity provider without needing a CustomGPT account. Standard includes 3 team members and Premium includes 5, but seat-free end-user access is available only on Enterprise with SSO already configured.
Can I white-label AI agents and let clients log in with their own SSO?
Yes. Consulting firms can give clients secure access to project agents through the client’s own corporate login, and group mapping can route each user to the right agent. You can share access through a portal link or embed the agent in a website or intranet, and custom branding is available. As Stephanie Warlick put it, “Check out CustomGPT.ai where you can dump all your knowledge to automate proposals, customer inquiries and the knowledge base that exists in your head so your team can execute without you.” IdP-based client access is an Enterprise feature and requires SSO to be configured first.
How is end-user IdP access different from regular SSO or ChatGPT SSO?
Regular SSO signs your internal team members into the AI workspace with company credentials. End-user IdP access signs students, clients, partners, or members into specific agents without turning them into workspace users or requiring separate accounts. That is the key difference from seat-based tools such as ChatGPT or Claude, where access is typically tied to user seats. End-user IdP access is available only on Enterprise after SSO is already set up.
How hard is it to set up SSO for AI agents?
If your organization already uses a SAML 2.0 identity provider, setup is usually straightforward. Your IT team connects the IdP, maps user groups to agents, and then chooses how to deliver access: a single portal link or an embedded agent on a website or intranet. Supported providers include Microsoft Entra ID, Okta, Google Workspace, PingOne, and other SAML 2.0 systems. You must have Enterprise SSO configured before end-user IdP access can be enabled.
How secure is IdP-based access for sensitive documents or multi-client deployments?
Ontop shows why controlled access matters for sensitive workflows: “CustomGPT.ai has transformed our operations by streamlining our legal team’s process. Our AI Agent, ‘Barry,’ handles over 100 questions weekly, reducing response time from 20 minutes to 20 seconds and saving our legal team 130 hours per month.” For sensitive or multi-client deployments, users authenticate through SAML, sessions last 24 hours, end-users are never stored as accounts, and group-to-agent mapping limits who can reach which agent. Security credentials include SOC 2 Type 2, GDPR compliance, and a policy that data is not used for model training.
Can I pilot with team seats first and then move to seat-free IdP access later?
Yes. You can start on Standard or Premium while a small internal team builds and tests agents, then move to Enterprise when you need authenticated access for a larger audience. Standard is $99/month with 3 team members, Premium is $499/month with 5 team members, and Enterprise uses custom pricing. To use end-user IdP access, your Enterprise account must already have SSO configured.