Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:ff20bd0db7f9…

Agent report card

Can an agent use GitHub REST API through Repository operations?

Grade B: Only part of the applicable terms is machine-readable.

GitHub / active

Agent ReadinessBLimited
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Limited

    Only part of the applicable terms is machine-readable.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Eligibility can be decided from explicit public criteria.

    Pricing or the absence of a charge is explicit and machine-readable.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility

    supported: fresh

    Eligibility can be decided from explicit public criteria.

    Eligibility criteria for GitHub services are explicitly detailed in the terms of service, including account requirements, age limits, and trade control restrictions.

    decidable_eligibility: Ready: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    GitHub REST API documentation explicitly details the product and repository operation endpoints, enabling full machine discovery.

    machine_discovery: Ready: tested 7 Aug

    Method http 1

    Readable pricing

    supported: fresh

    Pricing or the absence of a charge is explicit and machine-readable.

    Pricing information is explicitly detailed across public plan tiers including free options for public and private repositories.

    readable_pricing: Ready: tested 7 Aug

    Method http 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    Terms of Service are provided as structured HTML documentation on public web pages rather than a machine-readable schema endpoint.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What would improve this stage

    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Limited

    Only part of the signup flow is machine-operable.

    Whether CAPTCHA blocks signup has not been established.

    A stable signup entrypoint is available.

    The tested signup path does not require phone or SMS verification.

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Evidence and actions

    CAPTCHA-free signup unknown

    supported: fresh

    Whether CAPTCHA blocks signup has not been established.

    Documentation alone cannot establish the absence or presence of a CAPTCHA during the sign-up process.

    captcha_free: Unknown: tested 7 Aug

    Method headless 1

    Machine-operable signup limited

    supported: fresh

    Only part of the signup flow is machine-operable.

    The sign-up flow includes documented web steps and email verification prompts, requiring human intervention rather than a fully machine-operable automated API endpoint.

    machine_operable_form: Limited: tested 7 Aug

    Method headless 1

    Phone-free signup

    supported: fresh

    The tested signup path does not require phone or SMS verification.

    The documented signup steps require an email address and email verification, but do not require phone or SMS verification.

    phone_verification_free: Ready: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    A stable public signup entrypoint is available at https://github.com/signup.

    stable_entrypoint: Ready: tested 7 Aug

    Method http 1

    Supported identity flow

    supported: fresh

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    GitHub REST API documents scoped, revocable machine authentication methods including fine-grained personal access tokens and GitHub Apps with explicit authorization boundaries.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

    What would improve this stage

    • Expose labelled, deterministic controls and documented validation without requiring hidden human interaction.

  3. Pay

    Ready

    The required price or no-charge status is explicit before commitment.

    Machine-operable checkout has not been established.

    A supported payment rail has not been established.

    The tested funnel can complete without sales intervention.

    Evidence and actions

    Explicit price

    supported: fresh

    The required price or no-charge status is explicit before commitment.

    GitHub explicitly lists pricing details on its pricing page, including $0 USD per month for the Free plan, $4 USD per user/month for the Team plan, and $21 USD per user/month for Enterprise.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout unknown

    supported: fresh

    Machine-operable checkout has not been established.

    Retained evidence describes the signup documentation and general account creation steps, but does not provide headless operational observations to verify machine-operable checkout controls.

    machine_operable_checkout: Unknown: tested 7 Aug

    Method headless 1

    Sales-free purchase

    supported: fresh

    The tested funnel can complete without sales intervention.

    Users can sign up for a GitHub personal account directly online via the sign-up page or social logins without requiring sales intervention.

    sales_intervention_free: Ready: tested 7 Aug

    Method headless 1

    Supported payment rail unknown

    supported: fresh

    A supported payment rail has not been established.

    Retained headless evidence from the account documentation does not establish or demonstrate supported payment rails during the signup flow.

    supported_payment_rail: Unknown: tested 7 Aug

    Method headless 1

  4. Provision

    Ready

    Successful onboarding automatically activates usable access.

    A bounded provisioning delay has not been established.

    Usable credentials or delegated access are delivered through a documented flow.

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Evidence and actions

    Automatic activation

    supported: fresh

    Successful onboarding automatically activates usable access.

    Organization repositories are automatically created and activated upon calling the POST /orgs/{org}/repos REST API endpoint.

    automatic_activation: Ready: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    The retained documentation does not specify a documented time bound or completion guarantee for repository creation.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

    Usable credentials or delegated access are delivered through a documented flow.

    GitHub REST API documents standard credential delivery mechanisms including personal access tokens, GitHub App access tokens, and workflow GITHUB_TOKENs.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status

    supported: fresh

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Repository creation responds synchronously with a full JSON representation of the created repository object, including machine-readable status fields.

    machine_readable_status: Ready: tested 7 Aug

    Method http 1

  5. Operate

    Ready

    A documented API or tool interface is available for operation.

    An agent protocol interface has not been established.

    Authentication is documented and usable within an agent authorization boundary.

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access

    supported: fresh

    A documented API or tool interface is available for operation.

    GitHub REST API documentation provides documented API endpoints and interfaces for repository operations.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery

    supported: fresh

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Troubleshooting documentation provides credential revocation guidelines, retry waiting periods using headers, and failure recovery steps.

    delegated_recovery: Ready: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Repository operations endpoints document rate limits, structured HTTP error status codes, and request parameter validation rules.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    REST API documentation establishes usable token-based authentication via personal access tokens, GitHub Apps, and GITHUB_TOKEN Bearer headers.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

What works

  • Pay: The required price or no-charge status is explicit before commitment.
  • Provision: Successful onboarding automatically activates usable access.
  • Operate: A documented API or tool interface is available for operation.

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.
  • Sign up: Only part of the signup flow is machine-operable.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzf0m4x9v5n7pd3j2gc8q1fk
Revision
sha256:ff20bd0db7f9047c42b074b682e802c235f4fb273f1394dddd60191e6f5d2e8f
Projection
sha256:30794560ae2486f217717f025c549a7c0d570ab1248a116a15ccdde4acf0ab3f
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6