# Webhook Relay Trigger

> Webhook Relay Trigger is a paid API for AI agents from webhook-api-production-4378.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Triggers a named event on a registered webhook relay, forwarding an optional payload to subscribed listeners.

## Facts

- Endpoint: POST https://webhook-api-production-4378.up.railway.app/trigger?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webhook-relay-trigger-baaf83e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KvPGKcM4pEexabY5m8btf

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 webhook-relay-trigger-baaf83e0 -d '<json body>'
```

Example prompt: Trigger a webhook relay event called 'order.completed' with a payload containing orderId '12345' and status 'shipped'.

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-use webhook relay to dispatch named events to pre-registered listeners without managing your own webhook infrastructure. Ideal for automation pipelines, event-driven integrations, and IoT or CI/CD notification workflows where you want to fire-and-forward events on demand.

## Known failure modes

- Missing required 'event' field returns a 400 validation error
- Unregistered or inactive webhook destination may cause silent delivery failure
- Malformed payload object may cause a 422 or parsing error
- Network timeout on downstream relay delivery may result in partial delivery
- Payment failure (x402) prevents the trigger from executing

## How this service works

Event relay. Register a webhook, trigger events.

## Output

A confirmation response indicating the event was received and relayed to registered webhook listeners, typically including delivery status or acknowledgment details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "event"
 ],
 "properties": {
  "event": {
   "type": "string"
  },
  "payload": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webhook-relay-trigger-baaf83e0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from webhook-api-production-4378.up.railway.app](https://www.zero.xyz/host/webhook-api-production-4378.up.railway.app/llms.txt)