GitLab Container Registry · API Governance Rules

GitLab Container Registry API Rules

Spectral linting rules defining API design standards and conventions for GitLab Container Registry.

0 Rules
View Rules File View on GitHub

Spectral Ruleset

Raw ↑
x-aid: gitlab-container-registry:rules
x-name: GitLab Container Registry Rules
description: Operational rules and constraints for using the GitLab Container Registry API.
rules:
  - name: Authentication Required
    description: All API calls require a PRIVATE-TOKEN header or OAuth2 bearer token.
  - name: Permission Scopes
    description: Operations require an access token with the api scope.
  - name: Bulk Tag Deletion
    description: Bulk tag deletion requires either name_regex_delete or keep_n combined with older_than parameters.
  - name: Asynchronous Operations
    description: Repository and bulk tag deletion operations are processed asynchronously and return 202 Accepted.
  - name: Cleanup Policies
    description: Cleanup policies can be configured per project to automatically expire tags.
  - name: Rate Limits
    description: GitLab.com applies rate limits to API calls; consult GitLab documentation for current limits.

Work with this as data

Every ruleset here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/gitlab-container-registry-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.