{"resourceId":"uab-chatgpt-edu-credit-tiers-codex-mcp-20261030","versions":[{"version":"external-39b6bd903c873b308e12f0d1b7dc97d3d0ce02ca674958925dd66125fcec7355","resource":{"id":"uab-chatgpt-edu-credit-tiers-codex-mcp-20261030","title":"UAB restructures ChatGPT Edu into three credit-metered tiers, putting Work, plugins, Codex and MCP connections behind higher prices","organization":"University of Alabama at Birmingham (UAB) IT","sector":"Higher education","geography":"Birmingham, Alabama, United States","publishedAt":"October 30, 2026","publicationDate":"2026-10-30","eventDate":null,"sourceName":"UAB IT News","sourceLabel":"UAB IT: New UAB ChatGPT Edu service options planned","sourceUrl":"https://www.uab.edu/it/news/item/new-uab-chatgpt-edu-service-options-planned","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["governance-procurement","developers-agents","knowledge-work"],"finding":"UAB will offer faculty and staff three ChatGPT Edu tiers: Basic (chat, 450 credits a month, $29.25), Intermediate (adds ChatGPT Work and plugins, 900 credits, $49.50) and Advanced (adds Codex and approved MCP server connections, 2,200 credits, $108). Existing subscribers move automatically to Intermediate, Codex subscribers to Advanced; Advanced users can buy up to three 1,000-credit packs at $45 a month. Access requires acknowledging UAB Responsible AI Use, and plugins and connections must pass UAB data-handling approval.","sledRelevance":"A public research university is metering agentic features (Work, Codex, MCP) by credits and tier, a concrete model for how campuses and agencies can budget and gate OpenAI agent capability rather than buying flat seats.","evidence":"Operator notice with specific prices and credit allotments. No usage, cost-per-task or adoption data; unclear whether the prices are internal chargebacks or OpenAI list pricing.","architectureImplications":"MCP server connections are limited to the top tier and to UAB-approved servers, so agent access to institutional systems is an explicitly governed integration rather than a default.","governanceImplications":"Ties capability tier to a responsible-use acknowledgment and to approval of plugins and data connections; a template for tiered agent governance.","securityPrivacyImplications":"Codex and MCP connections widen data and system access; UAB relies on an approval process for connections, details of which are not published.","caveats":"Interpretation: credit allotments are not translated into task volumes, so budget adequacy is unknown. Students are excluded. Pricing applies to UAB only.","streamIds":["openai"],"roles":{"sales":"Sales framing: UAB shows campuses moving from flat Edu seats to credit-metered tiers, with agent features priced higher. That opens conversations about forecasting credit consumption and choosing who needs Work, Codex or MCP. Interpretation: buyers will want usage data before committing departments to the Advanced tier, and nothing here shows cost savings.","engineering":"Engineering framing: the key design choice is gating MCP server connections to an approved list at the top tier. Pre-sales should map which institutional systems would be exposed through MCP and what approval workflow applies. Limited applicability: UAB does not publish its approval criteria or credit-to-usage conversion.","delivery":"Delivery framing: tier migration and credit monitoring become ongoing operations. The operational owner is central IT with department budget holders. Proposed acceptance: a credit-usage dashboard by tier and a documented MCP connection approval process before broad Advanced enrollment."},"roleDetails":{"sales":{"customerProblem":"Campuses need a way to budget and govern agentic ChatGPT features without giving every user the most expensive, most connected tier.","stakeholders":["CIO and central IT","Department budget holders","Research computing","Information security office"],"discoveryQuestions":["How many users actually need Codex or MCP connections?","How will you forecast credit consumption by tier?","Who approves an MCP server connection?"],"valueHypothesis":"Tiering may match spend to need and keep agent connections behind review, if usage data supports the tier choices.","potentialEngagement":"A bounded credit-consumption and tier-fit analysis for one department over one billing cycle.","unsupportedClaims":["That tiering lowers total cost","That 2,200 credits covers typical Codex workloads","That MCP connections are secure by default"]},"engineering":{"fit":"Higher-ed and agency ChatGPT Edu/Enterprise workspaces offering Work, Codex and MCP.","architectureIntegration":"Approved MCP servers connecting ChatGPT to institutional systems; plugins subject to data-handling review.","prerequisites":["MCP connection approval process","Responsible-use policy","Usage reporting"],"constraints":["Faculty and staff only","Approval criteria unpublished","Credit-to-usage mapping unknown"],"security":"Each MCP server is a new data path; require scoped credentials, logging and data-classification review per connection.","proofOfValue":["Measure credit burn for a sample of Codex tasks","Pilot one approved MCP connection with access logging"]},"delivery":{"work":"Migrate subscribers to tiers, monitor credits, and run MCP/plugin approvals.","dependencies":["Billing data from OpenAI","Security review capacity"],"ownership":"Central IT with department budget holders.","skillsAdoption":"Guidance on which tasks justify Work or Codex use and how credits are consumed.","governanceCheckpoints":["Security review per MCP connection","Quarterly tier-fit review"],"acceptanceCriteria":["Credit usage reported by tier monthly (proposed)","All MCP connections documented with approval record (proposed)"],"risks":["Credit overruns","Unreviewed data exposure via connections","User confusion over tier changes"]}},"retrievedAt":"2026-11-01T03:09:29Z","enrichedAt":"2026-11-01T03:13:33Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Higher tiers may concentrate agent capability among departments able to pay.","procurementImplications":"Shows a consumption-metered, tiered internal offering on top of an OpenAI Edu agreement; procurement should obtain credit-to-usage definitions.","operatingModelImplications":"Turns AI provisioning into an ongoing chargeback and approval service run by central IT.","peerReview":"unknown","sourceVerification":{"openedUrl":"https://www.uab.edu/it/news/item/new-uab-chatgpt-edu-service-options-planned","referenceExcerpt":"Includes Intermediate features, ChatGPT Codex, and approved MCP server connections. It provides 2,200 credits per month at a monthly cost of $108.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}