# httpay.xyz GitLab API Gateway

> httpay.xyz GitLab API Gateway is a paid API for AI agents from httpay.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Proxies any GitLab REST API request through a pay-per-call gateway, forwarding arbitrary paths and methods to the GitLab API on behalf of the caller.

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/gitlab/%7B*path%7D/*
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-0c18772b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JqTUGJAQMwfJB6eqpKio8

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability httpay-xyz-0c18772b -d '<json body>'
```

Example prompt: Use the GitLab API gateway to list all open merge requests in the project namespace 'myorg/myrepo' — forward a GET to /api/v4/projects/myorg%2Fmyrepo/merge_requests?state=opened.

## When to prefer this

Use this endpoint when an AI agent needs to interact with the GitLab API without provisioning its own GitLab credentials or managing API keys directly — ideal for ephemeral, pay-per-use access to GitLab resources. Prefer this over direct GitLab API access when operating in a context that supports x402 micropayments and you want a single unified gateway pattern.

## Known failure modes

- Invalid or inaccessible GitLab path returns 404 or 400 from upstream
- Missing or insufficient GitLab authentication credentials cause 401/403
- Rate limiting by GitLab upstream returns 429
- Malformed request body causes 422 from GitLab
- Payment failure or insufficient USDC balance causes 402 and request is not forwarded

## How this service works

API Gateway: GitLab API

## Output

The raw JSON response from the GitLab REST API corresponding to the forwarded path — could include repository info, pipeline status, issue lists, merge request details, user profiles, or any other GitLab resource depending on the path called.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-0c18772b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from httpay.xyz](https://www.zero.xyz/host/httpay.xyz/llms.txt)