# ZenVault Pull-Based Work Queue

> ZenVault Pull-Based Work Queue 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 pull-based work queue with lease-based task distribution, automatically requeueing tasks whose leases expire before completion.

## Facts

- Endpoint: POST https://api.zenvault.eu/v1/queues?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-pull-based-work-queue-0d34c4de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_juWRNXbiRBTW5ylYXesfw

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-pull-based-work-queue-0d34c4de -d '<json body>'
```

Example prompt: Set up a pull-based work queue called 'image-processing-jobs' with a 60-second lease timeout so that if a worker crashes mid-task, the job automatically comes back for another worker to pick up.

## When to prefer this

Choose this endpoint when you need a durable, pull-based work queue where multiple agent workers independently claim tasks and lease timeouts protect against lost work from crashes or hangs. It is especially appropriate for distributed agent workflows running on ZenVault's infrastructure, where sibling services (key-value storage, webhook buffering, run-state resumption) are also in use. Prefer it over a simple message queue when automatic lease expiry and requeue semantics are required — i.e., when you cannot guarantee that every worker will acknowledge completion.

## Known failure modes

- Invalid or missing lease timeout configuration returns a 400 error
- Duplicate queue name conflict if queue already exists
- Payment failure via x402 protocol blocks queue creation
- Management token lost if not captured at creation — cannot be re-retrieved
- Queue not found if management token is used after queue expiry or deletion

## How this service works

Pull-based work queue with leases; timed-out leases requeue.

## Output

Returns the newly created queue resource (with its ID and configuration) plus a one-time management token that can be used to administer the queue (delete it, inspect it, or modify settings). The management token is only returned at creation time and must be stored securely.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zenvault-pull-based-work-queue-0d34c4de/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)