Agent report card
Can an agent use GitHub Enterprise Server 3.21 through Repository operations?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayBlocked
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
GitHub Enterprise Server and its REST API documentation are explicitly discoverable, including REST API overview and quickstart entrypoints.
Only some material eligibility conditions are decidable before commitment.
Applicable terms are stable, readable, retrievable, and materially complete.
Price or no-charge status, variables, currency, and material conditions are explicit.
Verified structured artifacts accelerate discovery of the evaluation surface.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshOnly some material eligibility conditions are decidable before commitment.
GitHub Enterprise Server combined use requires an enterprise account on GitHub Enterprise Cloud or contacting GitHub Sales to create one. For metered usage-based licensing, users must first be assigned to a GitHub Enterprise Cloud organization, and Server version 3.13+ with GitHub Connect is required.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
GitHub Enterprise Server can be set up at no additional cost with an enterprise account. Under metered usage-based licensing, Cloud users automatically receive a right to use Server and billing is based on active monthly users.
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 and its REST API documentation are explicitly discoverable, including REST API overview and quickstart entrypoints.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
Documentation explicitly states that the GitHub REST API is fully described in an OpenAPI compliant document.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
Applicable GitHub Terms of Service are stable, readable, and retrievable, covering Account Terms, Acceptable Use, Payment, and Supplemental Terms.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained documentation addresses API authentication methods and rate limits but does not declare a specific web agent access or crawler policy for the assessed resources.
Only part of the access flow is operable or a bounded human step remains.
Setting up a trial of GitHub Enterprise Server involves submitting a trial request, following prompts via an emailed link, downloading a license file, and uploading it to install the instance.
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 involves submitting a trial request, following prompts via an emailed link, downloading a license file, and uploading it to install the instance.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable canonical trial path is documented for setting up a trial of GitHub Enterprise Server, where users submit a trial request and complete installation.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence does not contain explicit first-party declarations or direct observations regarding CAPTCHA requirements or verified-agent alternatives.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Scoped access tokens, fine-grained personal access tokens, GitHub App tokens, and OAuth tokens can be generated and authenticated against the REST API. Tokens can expire and can be revoked by the user or application.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence does not state whether phone verification is required, absent, or supported through a safe resumable boundary.
What would improve this stage
- Expose deterministic controls, validation, and resumable authorization handoffs.
Paid access requires opaque or unbounded sales intervention.
GitHub Enterprise Server license documentation explicitly states that purchasing, renewing, adding user licenses, or upgrading requires contacting GitHub's Sales team.
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 for GitHub Enterprise Server describes license acquisition and upgrades via GitHub's Sales team or downloading license files after order completion, but does not document an automated or protocol-driven checkout construction, handoff approval, and resumption flow.
Is the exact commercial commitment disclosed before authorization?
supported: freshThe public commitment omits a material component until later in the flow.
GitHub Enterprise billing documentation discloses usage-based (metered) and volume/subscription billing models, noting that usage-based billing is billed monthly based on active users, but volume agreements and specific commercial commitments require 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 retained documentation notes that licenses are acquired or upgraded through GitHub's Sales team or generated via Enterprise account settings, but does not document a delegated payment authorization rail with explicit human-confirmed authority or receipts.
Is a direct self-service path to paid access documented?
supported: freshPaid access requires opaque or unbounded sales intervention.
GitHub Enterprise Server license documentation explicitly states that purchasing, renewing, adding user licenses, or upgrading requires contacting GitHub's Sales team.
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.
GitHub Enterprise Server REST API authentication tokens can be generated (such as personal access tokens or GitHub App tokens) or created by app owners on an app settings page, where client IDs and client secrets are displayed and used to create access tokens.
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 tokens can be generated (such as personal access tokens or GitHub App tokens) or created by app owners on an app settings page, where client IDs and client secrets are displayed and used to create access tokens.
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 the REST API returns a synchronous 201 Created HTTP response status code upon successful resource creation.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Repository creation can be triggered via a REST API POST request to /orgs/{org}/repos, which returns a 201 Created response containing the repository resource details.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
Safe failure handling is documented only partially.
Documentation establishes rate limit error codes (403 Forbidden, 429 Too Many Requests), headers (retry-after, x-ratelimit-remaining, x-ratelimit-reset), retry guidelines with exponential backoff, and timeouts (terminated after 10 seconds). Full idempotency, cancellation, and reconciliation semantics across all operations remain partially documented.
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?
supported: freshCurrent admissible evidence does not resolve this finding.
Current admissible evidence does not resolve an agent-native protocol interface such as MCP or A2A for the targets.
- enterprise-repository-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
First-party documentation establishes that tokens can expire or be revoked, and access tokens created by a GitHub App expire after eight hours and can be regenerated using a refresh token. However, a full programmatically automated credential lifecycle covering compromise response and recovery without manual intervention is not fully established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Documentation establishes rate limit error codes (403 Forbidden, 429 Too Many Requests), headers (retry-after, x-ratelimit-remaining, x-ratelimit-reset), retry guidelines with exponential backoff, and timeouts (terminated after 10 seconds). Full idempotency, cancellation, and reconciliation semantics across all operations remain partially documented.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Request-time authentication to the REST API is documented and usable via the Authorization header using Bearer tokens (including GitHub Actions GH_TOKEN) or fine-grained tokens with explicit scoped permissions.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Essential target endpoints and REST API operations have stable, readable request parameters, HTTP methods, response schemas, status codes, rate-limit point calculations, error formats, and documented OpenAPI description accessibility.
- 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 documented across the REST API has a stable, usable machine interface alternative via documented HTTP REST endpoints.
- 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
- Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
What blocks agents
- Pay: Paid access requires opaque or unbounded sales intervention.
Where autonomy is limited
- Sign up: Only part of the access flow is operable or a bounded human step remains.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
What this grade establishes
14 of 14 graded signals have current supporting evidence. 1 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.
How the grade is derived
A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.
Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.
Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.
Startup offers
GitHub on the startup-offers board
- $10,000 in creditsGitHub for Startups Offer
Distribution
The grade’s badge
One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.
[](https://sourcey.com/log/github/agent-readiness/github-enterprise-server-3-21/repository-operations)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01m0ewej9qyk04qypr2mvmwmh1
- Projection
- sha256:9ce56e92fd056bf6e396f908920196f5e5ae85a98f55ad85696913a0d88db92d
- Policy
- service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration