# Gitera

> Gitera is a GitHub Actions observability platform for organization-wide workflow monitoring, log search, cost and runner analysis, failure investigation, notifications, workflow management, reusable workflow tracking, security policies, and read-only AI-assisted analysis.

Gitera helps platform engineering and DevOps teams understand GitHub Actions across many repositories from one place. Public resources below are available without authentication. Authenticated application APIs are not yet offered as a stable third-party integration surface and are intentionally omitted from the public OpenAPI specification.

## Developer resources

- [Gitera Developer Resources](https://gitera.io/developers): Human-readable API scope, formats, authentication expectations, errors, and discovery links.
- [Gitera API Authentication](https://gitera.io/developers#authentication): Public endpoint authentication requirements and current credential availability.
- [Gitera Webhooks](https://gitera.io/developers#webhooks): Current public webhook support and integration limits.
- [Gitera MCP Server](https://gitera.io/developers#mcp): Current Model Context Protocol support and recommended agent interface.
- [Gitera API Versioning and Deprecation Policy](https://gitera.io/developers#versioning): URL-path versioning, the `Gitera-Api-Version` header, and the `Deprecation`/`Sunset` retirement signals.
- [Gitera OpenAPI Specification](https://gitera.io/openapi.json): OpenAPI 3.1 description of supported public endpoints.
- [Gitera Versioned Public API](https://gitera.io/api/v1): Canonical versioned base path, including the machine-readable `versioning` policy object.
- [Gitera Versioned Service Health](https://gitera.io/api/v1/health): Public JSON service and dependency health on the versioned base path.
- [Gitera Public API Index](https://gitera.io/api): JSON index of stable public endpoints and machine-readable resources. Permanent alias for the current major version.
- [Gitera Service Health](https://gitera.io/api/health): Public JSON service and dependency health.
- [Gitera API Catalog](https://gitera.io/.well-known/api-catalog): RFC 9727 API catalog linkset.
- [Gitera Agent Skills](https://gitera.io/.well-known/agent-skills/index.json): Agent Skills Discovery index.
- [Gitera Sitemap](https://gitera.io/sitemap.xml): Index of public product, platform, blog, and legal pages.
- [Gitera Robots Policy](https://gitera.io/robots.txt): Search, AI input, and AI training crawler directives.

## Agent-readable product content

Gitera supports Markdown content negotiation on the homepage, platform pages, blog pages, and legal pages. Send `Accept: text/markdown` to the canonical page URL. Agents can also request [Gitera Homepage Markdown](https://gitera.io/api/md?path=/) directly. HTML remains the default representation.

- [Gitera Homepage](https://gitera.io/): Product overview and entry point.
- [Gitera Platform](https://gitera.io/#features): GitHub Actions observability capabilities.
- [Gitera Blog](https://gitera.io/blog): Guides for GitHub Actions operations and observability.
- [Gitera Terms of Service](https://gitera.io/legal/terms): Service terms.
- [Gitera Privacy Policy](https://gitera.io/legal/privacy-policy): Data and privacy policy.

## API behavior

Supported public API responses are JSON. Errors on public API discovery routes use RFC 9457 Problem Details with the media type `application/problem+json`. Error objects include a stable `code`, a human-readable `detail`, a `resolution` hint, and a `documentation` URL. Use the OpenAPI specification as the authoritative list of supported public paths and methods.

## API versioning and deprecation

The Gitera public API is versioned in the URL path. `https://gitera.io/api/v1` is the canonical base path for the current major version and is the path agents should integrate against. `https://gitera.io/api` is a permanent alias that always resolves to the current major version, so its response shape follows whichever version is current.

Every versioned discovery and health endpoint (`/api`, `/api/v1`, `/api/health`, `/api/v1/health`) carries the `Gitera-Api-Version` header, currently `v1`. Breaking changes - removing an endpoint or field, or changing an existing response shape - are released only under a new path segment such as `/api/v2`. Additive, backwards-compatible changes are released within the current version.

A version scheduled for retirement returns `Deprecation` (RFC 9745) with the date it was declared deprecated, `Sunset` (RFC 8594) with the HTTP-date it stops responding, and a `Link` header with `rel="deprecation"` and `rel="successor-version"`. A deprecated version keeps responding for at least 183 days after the `Deprecation` header first appears. No Gitera API version is deprecated today. The machine-readable form of this policy is the `versioning` object in the `/api/v1` response.