# httpay.xyz API Gateway: Slack Web API

> httpay.xyz API Gateway: Slack Web API 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 authenticated calls to the Slack Web API via a pay-per-call x402 micropayment gateway, eliminating the need for API keys

## Facts

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

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-api-gateway-slack-web-api-1941f63e -d '<json body>'
```

Example prompt: Post a message to our #alerts Slack channel saying 'Deployment to production completed successfully at 3:45pm' — use the pay-per-call Slack gateway so we don't need to manage API keys.

## When to prefer this

Choose this endpoint when an AI agent needs to call the Slack Web API without managing OAuth tokens or API keys, and is already operating in a USDC/x402 micropayment context. Ideal for serverless agents or automation workflows that need occasional Slack notifications without the overhead of credential management.

## Known failure modes

- 402 Payment Required if USDC payment header is missing or insufficient
- Invalid Slack path results in 404 from underlying Slack API
- Slack API rate limiting returns 429 too many requests
- Malformed request body causes Slack API validation error
- Slack channel not found or bot not invited returns channel_not_found error
- Payment settlement failure causes gateway to reject the request

## How this service works

API Gateway: Slack Web API

## Output

Returns the raw Slack Web API JSON response for the proxied request — typically includes 'ok: true', message timestamp, channel ID, and any relevant Slack-specific metadata or error details if the call fails.

## More

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