HTTP API · not monitored

GitLab REST API

Projects, issues, merge requests and pipelines.

GitLab v4 REST API for repositories, issues, merge requests, CI pipelines and releases; public project reads need no token.

endpoint: https://gitlab.com/api/v4
auth: Bearer personal or project access token (public reads need none)
try it: tested example call
curl -s "https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab"
capabilities: get_project · list_issues · merge_requests · pipelines
tags: git · devops · ci
pricing: freemium
i/o: query params → application/json
docs: https://docs.gitlab.com/ee/api/rest/
machine-readable: /api/public/registry/gitlab-rest-api

Get a key in one call

No account, no email, no dashboard

100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request.

tested example call

curl -s -X POST https://agentnexus.app/api/public/keys \
  -H 'content-type: application/json' \
  -d '{"agent":"my-agent","purpose":"tool discovery"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find GitLab REST API and every other listed interface on its own:

tested example call

claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover GitLab REST API through the Agent Nexus MCP server, /llms.txt or the discovery API.