Agent report card
Can an agent use GitHub Enterprise Server 3.21 through Repository operations?
Grade D: Paid access requires opaque or unbounded sales intervention.
GitHub / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateLimited
- Sign upLimited
- PayBlocked
- ProvisionLimited
- OperateLimited
Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
The pricing model is visible but omits a material variable or condition.
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Eligibility conditions and required inputs are explicit and decidable.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
GitHub Enterprise Server eligibility conditions and required inputs are explicit: users are entitled to use GitHub Enterprise Server with the GitHub Enterprise plan, with deployment options including GHE Usage-based (requiring active assignment to a GitHub Enterprise Cloud organization) or Volume/Subscription licensing.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshThe pricing model is visible but omits a material variable or condition.
The evidence outlines the pricing mechanisms (such as active user monthly billing for metered licenses and GitHub Codespaces rates starting at $0.18/hr compute and $0.07/GB storage), but volume subscription terms require contacting GitHub Sales, leaving fixed-cost volume variables contextual.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
GitHub Enterprise Server is documented as a self-hosted platform deployment option, and the GitHub REST API documentation provides quickstart guides, OpenAPI descriptions, and endpoints for managing integrations and workflows.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshTerms are readable but materially incomplete, ambiguous, contextual, or unstable.
The GitHub Terms of Service are retrievable, but Section J.1 states that if the use of the service is governed by a GitHub Customer Agreement or volume licensing agreement, specific enterprise terms apply rather than the general individual terms.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
What would improve this stage
- Publish complete applicable terms at a stable public URL.
- Publish readable complete pricing or explicit no-charge status and conditions.
Only part of the access flow is operable or a bounded human step remains.
A stable canonical route begins the required access bootstrap.
Scoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshOnly part of the access flow is operable or a bounded human step remains.
Setting up a trial of GitHub Enterprise Server requires submitting a trial request to obtain a link by email to set up an account for the GitHub Enterprise Web portal, followed by downloading and uploading a license file.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable canonical trial request route is available to begin setting up a trial of GitHub Enterprise Server.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
Current admissible evidence does not contain explicit declarations or direct observations regarding CAPTCHA requirements during the trial or license acquisition flows.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
GitHub Enterprise Server REST API supports authenticating with scoped personal access tokens, GitHub App tokens, and OAuth app tokens, which can be expired or revoked by users or applications.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
Current admissible evidence does not mention phone verification requirements or supported boundaries for GitHub Enterprise Server sign-up or license acquisition.
What would improve this stage
- Expose deterministic controls, validation, and resumable authorization handoffs.
Paid access requires opaque or unbounded sales intervention.
The public commitment omits a material component until later in the flow.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence shows that license files are downloaded after purchasing or upgrading from GitHub's Sales team or via GitHub Enterprise Cloud settings, but it does not establish an end-to-end deterministic checkout flow with handoff approval and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshThe public commitment omits a material component until later in the flow.
GitHub discloses enterprise licensing billing models (usage-based/metered vs. volume) and feature allowances (such as Actions minutes), but material pricing details for volume/subscription licenses require custom sales agreements or manual setup via GitHub Sales.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The documentation mentions supported payment methods and invoice options for enterprise accounts, but it does not detail a payment authorization rail for scoped agent delegation or explicit human-confirmed authorization with receipts.
Is a direct self-service path to paid access documented?
supported: freshPaid access requires opaque or unbounded sales intervention.
Purchasing or upgrading a license for GitHub Enterprise Server explicitly requires contacting GitHub's Sales team, rather than offering a direct self-service purchase path.
What blocks agents
- Paid access requires opaque or unbounded sales intervention.
What would improve this stage
- Document a direct purchase path or bounded vendor review with machine-readable status.
- Disclose the complete commitment before payment authorization.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
GitHub Enterprise Server REST API authentication accepts personal access tokens, GitHub App tokens, and GitHub Actions GITHUB_TOKENs, and client secrets can be generated in app settings pages. However, the evidence leaves manual token generation and dashboard client secret retrieval as human-driven transfer steps without establishing a fully programmatic delivery path for all credentials.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshA synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Creating an organization repository via REST returns a synchronous HTTP 201 Created success response. Creating a repository using a template also returns an HTTP 201 Created response along with the usable repository object in the JSON body.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Provisioning a repository for an authenticated user can be initiated directly and deterministically by an authorized agent via an HTTP POST request to /user/repos.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
Safe failure handling is documented only partially.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Essential operations have stable readable request, response, and effect semantics.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Documentation establishes that personal access tokens can set an expiration date after which they are automatically revoked, and tokens can be revoked manually by the user or an OAuth app. However, current admissible evidence does not document a complete agent-executable secret rotation and recovery lifecycle.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
The REST API documentation defines rate limit failure modes (403 Forbidden and 429 Too Many Requests), standard response headers (retry-after, x-ratelimit-remaining, x-ratelimit-reset), and retry guidelines with exponential backoff. However, full cancellation and reconciliation semantics are not fully documented in the admitted evidence.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Request-time authentication is explicitly documented for REST API operations using scoped authority such as GitHub App user access tokens, installation tokens, or fine-grained PATs passed via the Authorization header using Bearer or token syntax.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
The REST API documentation provides stable parameters, HTTP methods, request headers, error status codes (e.g., 401, 403, 422), response schemas, and cURL/JavaScript code examples across troubleshooting, rate limiting, repository, and general REST endpoints.
- enterprise-repository-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Every essential target is accessible through documented machine-operable REST API endpoints, supported by code samples in cURL, JavaScript, and GitHub CLI.
- enterprise-repository-api
What would improve this stage
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
No stage is currently established as ready.
What blocks agents
- Evaluate: Terms are readable but materially incomplete, ambiguous, contextual, or unstable.
- Sign up: Only part of the access flow is operable or a bounded human step remains.
- Pay: Paid access requires opaque or unbounded sales intervention.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
Startup offers
GitHub on the startup-offers board
- $10,000 in creditsGitHub for Startups Offer
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01m0ewej9qyk04qypr2mvmwmh1
- Projection
- sha256:e9c5d4007d2b41f0f2a10306f7015a7b566e8d4b8026b42036e2a8d787fbbe41
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration