# httpay.xyz PagerDuty API Gateway

> httpay.xyz PagerDuty 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-15).

Proxies PagerDuty REST API calls through an x402 pay-per-use gateway, enabling incident management, alerting, and on-call scheduling operations via micropayment-authenticated requests.

## Facts

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

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-pagerduty-api-gateway-b5abf7a5 -d '<json body>'
```

Example prompt: Trigger a PagerDuty incident titled 'Database connection pool exhausted' on the service with ID P1234AB, with critical severity, and assign it to the on-call engineer on the backend escalation policy EP56789.

## When to prefer this

Use this endpoint when your agent needs to interact with the PagerDuty incident management API without managing a long-lived PagerDuty API key infrastructure, paying only per call via x402 USDC micropayments. Ideal for agents automating DevOps workflows, monitoring systems, or on-call automation that need occasional PagerDuty access.

## Known failure modes

- Invalid PagerDuty API path returns 404 not found
- Missing or invalid PagerDuty authentication token returns 401 unauthorized
- Malformed request body returns 400 bad request from PagerDuty
- Nonexistent resource ID (incident, service, schedule) returns 404 from PagerDuty
- Rate limit exceeded returns 429 too many requests
- x402 payment failure returns 402 payment required before proxying
- PagerDuty service outage returns 503 or timeout

## How this service works

API Gateway: PagerDuty API

## Output

Returns the raw PagerDuty API JSON response for the requested operation, which may include incident objects (id, status, title, urgency, assigned_to, created_at), service details, schedule records, or confirmation of state changes such as acknowledgment or resolution.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-pagerduty-api-gateway-b5abf7a5/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)