> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryreplicas.com/llms.txt > Use this file to discover all available pages before exploring further. # Report Automation GitHub Check > Reports an automation run's verdict on one of the GitHub check runs it owns. Requires in-workspace credentials (engine secret plus `X-Workspace-Id`): the calling workspace identifies the run that owns the check, so a check run ID is not a capability to write to any check in the organization. Replicas re-verifies ownership under the same lock every other writer takes before writing to GitHub, so a verdict from a run that has since been superseded is discarded rather than applied. ## OpenAPI ````yaml /openapi.json post /v1/automations/checks/{checkRunId} openapi: 3.1.0 info: title: Replica API version: 2.0.0 description: >- The Replica API allows you to programmatically manage cloud workspaces for AI agents. Use this API to manage environments (the org-scoped primitive workspaces are created from — including variables, files, skills, MCPs, warm hooks, start hooks, and warm pools), create and manage replicas, send messages, manage chats, stream events, read connected repositories and repository sets, and configure automations. servers: - url: https://api.tryreplicas.com description: Production API security: - apiKey: [] tags: - name: Environments description: >- Manage environments — the primitive that workspaces are created from. Variables, files, skills, MCPs, warm-hooks, and warm-pools are all scoped to an environment. Every organization has a singleton Global environment whose values apply to every workspace. Personal environments are scoped to the authenticated user and can be standalone or source-backed by a team environment. - name: Repository description: >- Read repositories and repository sets connected to your organization. Repositories are the underlying GitHub-connection layer; bind them to an environment to use them in workspaces. - name: Replica description: Manage replicas (workspaces) for AI agents - name: Terminal description: Manage interactive terminal sessions in active workspaces - name: Preview description: Manage public preview URLs for workspace ports - name: Profile description: Read and update the authenticated user's profile - name: Credentials description: >- Manage coding-agent credentials for an organization or the authenticated user - name: Google Search Console description: >- Read Search Console properties, performance, sitemaps, and URL inspection results through a connected Google account - name: Slack description: Connect Slack identities and route threads to Replicas workspaces - name: Linear description: Connect Linear identities to Replicas accounts - name: Automation description: >- Create and manage automations that trigger replicas on a schedule or in response to events - name: Downloads description: Download Replicas applications - name: Analytics description: >- Read aggregated activity and usage metrics for your organization: compute minutes, workspaces created by source, and pull request throughput over a time range. - name: Presence description: >- Read and report ephemeral member presence: who is online, where they are (environment or workspace), and whether they are typing. Presence is backed by short-lived keys rather than the database and broadcast to other members over the events stream. paths: /v1/automations/checks/{checkRunId}: post: tags: - Automation summary: Report Automation GitHub Check description: >- Reports an automation run's verdict on one of the GitHub check runs it owns. Requires in-workspace credentials (engine secret plus `X-Workspace-Id`): the calling workspace identifies the run that owns the check, so a check run ID is not a capability to write to any check in the organization. Replicas re-verifies ownership under the same lock every other writer takes before writing to GitHub, so a verdict from a run that has since been superseded is discarded rather than applied. operationId: reportAutomationCheck parameters: - name: checkRunId in: path required: true schema: type: integer description: GitHub check run ID, as given to the agent in its prompt. requestBody: required: true content: application/json: schema: type: object required: - token - conclusion - title properties: token: type: string description: >- Ownership token for this check run, as given to the agent in its prompt. Names which run the verdict came from, so a superseded run's verdict is discarded instead of overwriting a newer one. conclusion: type: string enum: - success - failure description: >- Only the two conclusions a merge gate reads unambiguously are accepted. title: type: string description: One-line verdict shown on the check. summary: type: string description: >- What was checked and why it passed or failed. Defaults to the title. responses: '200': description: Verdict processed content: application/json: schema: type: object required: - reported - name properties: reported: type: boolean description: >- False when a newer run of the automation owns the check and this verdict was discarded. name: type: string description: The check run's name. '400': description: Invalid token, conclusion, title, or check run ID '403': description: Not called with in-workspace credentials '404': description: The check run is not owned by the calling workspace components: securitySchemes: apiKey: type: http scheme: bearer description: >- API key authentication. Obtain your API key from the Replicas dashboard under Organization → Settings → API Keys. ````