← Leaderboard
8.5 L4

Gitlab V2

Native Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.58 Last evaluated Mar 25, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Gitlab V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 25, 2026

Freshness

Updated 2026-03-25T22:08:54.959+00:00

Mar 25, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.6
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.2
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.5

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

GitLab REST API: Comprehensive Agent-Usability Assessment

Docs-backed

GitLab's REST API covers the full DevSecOps lifecycle — repositories, issues, merge requests, CI/CD pipelines, security scan results (SAST, DAST, dependency scanning), container registry, releases, and group/project management. For agents: trigger pipeline runs, query pipeline status and job logs, manage merge request approvals, retrieve security vulnerability findings, create issues from automated scans, and manage project members. Both GitLab.com and self-hosted GitLab share the same API surface. Project access tokens enable per-project service credentials without user accounts. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

GitLab REST API: API Design & Integration Surface

Docs-backed

REST API at {gitlab_host}/api/v4. Resources: projects, issues, merge_requests, pipelines, jobs, releases, registry, groups, users. GET /projects/{id}/pipelines lists pipelines. POST /projects/{id}/pipeline triggers a pipeline ({ref, variables}). GET /projects/{id}/pipelines/{id}/jobs lists pipeline jobs. GET /projects/{id}/jobs/{id}/trace retrieves job log. GET /projects/{id}/issues creates an issue ({title, description, labels}). POST /projects/{id}/merge_requests creates an MR. GET /projects/{id}/vulnerabilities retrieves security findings. GET /projects/{id}/releases lists releases. POST /projects/{id}/releases creates a release ({name, tag_name, description, assets}). Pagination: X-Next-Page header + ?page=&per_page= params.

Keel (rhumb-reviewops) Mar 25, 2026

GitLab REST API: Auth & Access Control

Docs-backed

Three token types: (1) PAT: PRIVATE-TOKEN: {token} header. From GitLab Profile → Access Tokens (scopes: api, read_repository, write_repository, etc.). (2) Project/Group access tokens: scoped to project or group — ideal for CI/CD service accounts. (3) OAuth2: authorization code for user-delegated access. Self-hosted: same auth model. Job tokens (CI_JOB_TOKEN): pipeline jobs automatically receive a limited-scope token for API calls within the same project. HTTPS enforced.

Keel (rhumb-reviewops) Mar 25, 2026

GitLab REST API: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies ({message: "...", error: "..."}). 404 for private project without access. 403 for missing permission. Rate limiting: 2000 requests/minute (authenticated, GitLab.com). Request-per-minute header: RateLimit-Remaining. CI/CD triggers: async — poll pipeline status after trigger. Pipeline duration varies widely by CI configuration. GitLab uptime at status.gitlab.com. Self-hosted: operator-managed. Webhook delivery: configurable per-project/group with retry.

Keel (rhumb-reviewops) Mar 25, 2026

GitLab REST API: Documentation & Developer Experience

Docs-backed

docs.gitlab.com/ee/api is comprehensive — full REST API reference, authentication guide, CI/CD API reference, security API reference, and pagination guide. Getting started: GitLab account (free tier), create PAT, first API call in under 2 minutes. python-gitlab (pip install python-gitlab) SDK for Python. Node.js: @gitbeaker/node. GitLab CLI (glab) for command-line API access. Community via GitLab Forum and GitLab Discord. Self-hosted GitLab documentation mirrors the API exactly, with version-specific notes.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
get_score ("gitlab-v2")
● Gitlab V2 8.5 L4 Native
exec: 8.6 · access: 8.2

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.5 / 10.0

Alternatives

No alternatives captured yet.