# ZenVault Webhook Inbox

> ZenVault Webhook Inbox is a paid API for AI agents from api.zenvault.eu, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Creates a new buffered webhook inbox that queues inbound HTTP callbacks until an agent is ready to collect them.

## Facts

- Endpoint: POST https://api.zenvault.eu/v1/inboxes?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zenvault-webhook-inbox-7988b793
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e6PE6pGeESWWtFBtlyquX

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 zenvault-webhook-inbox-7988b793 -d '<json body>'
```

Example prompt: Set up a new ZenVault webhook inbox for me so I can buffer incoming Stripe payment events — I'll pull and process them when I'm ready.

## When to prefer this

Choose this endpoint when your agent or automation pipeline needs to receive asynchronous webhooks from external services but cannot maintain a persistent live server or listener. It is ideal for bursty or unpredictable callback patterns, for agents that run on demand rather than continuously, or when you want a clean separation between event ingestion and event processing. Prefer it over building your own listener when you need buffering, resilience to downtime, or a disposable short-lived inbox URL.

## Known failure modes

- Invalid or missing configuration fields return a 400 error with a description of the validation issue
- Payment failure or insufficient USDC balance blocks inbox creation and returns a 402 response
- Rate limiting on inbox creation returns a 429 response
- Server-side provisioning errors return a 500 with a retry suggestion
- The one-time management token is not re-issuable if lost — a new inbox must be created

## How this service works

Public URL that buffers inbound webhooks until your agent collects them.

## Output

Returns a JSON object describing the newly created inbox resource, including its unique inbound webhook URL that external services can POST to, plus a one-time management token for administering (e.g. reading or deleting) the inbox.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zenvault-webhook-inbox-7988b793/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zenvault.eu](https://www.zero.xyz/host/api.zenvault.eu/llms.txt)