Live at api.zenvault.eu — all 57 services, paid per call with x402 or prepaid credits

Your agent dies between runs.
Its infrastructure shouldn't.

ZenVault sells the properties of a persistent server to AI agents: scheduled wake-ups, public addresses, durable memory, watchful eyes and a line to the humans. No account, no API key, no signup — payment is the only credential. A paid API from the first call.

Read llms.txt and start Talk to the operator
No accountspayment is identity; a capability token per resource
Paid per usex402 micro-payments in USDC on Base, or prepaid credits — no free tier
Expiry by defaultevery resource has a TTL; extend it by paying again
Machine-firstllms.txt, OpenAPI and MCP discovery at launch

How it works

Three requests, no onboarding. Your agent already knows how to do this.

01

Call an endpoint

The API answers 402 Payment Required with exact terms: price, asset, receiving address.

02

Pay and retry

Attach an x402 payment (USDC on Base) or a prepaid credit token. Same price list either way.

03

Hold the token

You get your resource plus a management token: check status, extend the TTL, cancel, export. Lose it and the resource simply expires.

All 57 services

Six families, one theme: things only a machine that never sleeps can do for a process that always does. All of it is live today.

Time

Someone to wake you, delay for you, and swear to when things happened.

  • Wake-up call: your webhook, called at the moment you chose
  • Recurring schedule: a cron expression fires until prepaid time runs out
  • Dead-man switch: miss a check-in and we alert your human; check-in history stays queryable
  • Delayed delivery: hand us a payload now, we deliver it later
  • Drip queue: dump up to 100 items, delivered out at a fixed rate
  • Scheduled snapshot: we fetch a URL at time X and store what we saw
  • Load-spread scheduler: N calls spaced evenly over a window
  • Quiet-period debouncer: bursts in, one aggregate out after the noise stops
  • Timestamp notary: signed proof a hash existed at time T
  • Attested fetch: page content plus a signed receipt of url, status, hash and time

Address

A fixed place on the internet for a process that has none.

  • Webhook inbox: a public URL that buffers calls until you collect them
  • Agent front door: permanent URL, durable buffer, retry-until-ack forwarding, replay window
  • Request bin: full capture of headers, body and timing, for debugging
  • Webhook fan-out: one inbound call forwarded to N destinations with retries and logs
  • Stable address: a permanent URL that follows your agent wherever it runs
  • Guaranteed delivery: we POST until it succeeds, then hand you the receipt
  • OAuth callback receiver: a stable redirect URI that catches authorization codes
  • Payload transformer: deterministic remapping between webhook formats
  • Handshake responder: answers verification challenges while you're away
  • Auth-gated proxy: basic auth, bearer or IP allowlist in front of any URL
  • Human contact form: hosted form, submissions land structured in your inbox
  • Notification relay: reach your human on Telegram, Discord, Slack, ntfy, email and 100+ services
  • Human approval gate: propose an action, a human clicks approve or deny, the signed verdict comes back to you

Memory

State that survives you.

  • Scratch KV: key-value with TTL, shared across all your runs
  • Crash checkpoint: save mid-task, resume exactly there after dying
  • Append-only journal: a durable diary with cheap writes
  • One-time-read drop: the value self-destructs on first read
  • Blob parking: a file at a private URL, up to 100 MB for 48 h
  • Large object store: up to 2 GB for 7 days; we can fetch the URL for you
  • Versioned config: KV with history and rollback
  • Idempotency firewall: atomic check-and-consume of operation IDs
  • Work queue: push jobs, workers lease and ack, timeouts requeue
  • Atomic counters: increment, read, reset

Place

Publish something without owning a server.

  • Static page hosting: an HTML report at name.zenvault.eu for N days
  • Static site hosting: upload a zip, get a whole site, checksums verifiable by API
  • Expiring share links: short links with click stats and a TTL
  • HTML to PDF: rendered server-side, stored for pickup
  • Static egress connector: allowlisted calls from our fixed IP for IP-restricted APIs

Watching

Eyes that stay open while yours are closed.

  • Change watch: poll a URL, fire your webhook when the content changes
  • Heartbeat monitor: we ping your endpoint and alert when it goes quiet
  • Keyword watch: fire when a string appears on a page or feed
  • Structured watch: CSS selector or JSONPath with threshold conditions
  • Regex watch: your pattern, fired on appear, disappear or change
  • RSS to webhook: one call per new feed item, deduped
  • Content-drift threshold: alert only when a page changes more than N percent
  • Staleness alarm: the inverse watch; alert when something stops changing
  • Redirect watch: alert when a URL's final destination moves
  • Sitemap watch: new or removed pages on a site
  • DNS record watch: alert when a record's value changes
  • Cert-transparency watch: new certificates issued for a domain
  • Port watch: one host, one port, open or closed
  • Flap suppression: alert only after N consecutive confirmations
  • Watch composition: AND and OR across any of your watches
  • Escalation chain: webhook first, then email, then your human

Utilities

Heavy tools your runtime doesn't ship with.

  • Document conversion: HTML, Markdown and Office files to PDF
  • OCR: image or PDF in, text out, priced per page
  • Server-side transfer: move data between 70+ storage backends; bytes never touch your context

Platform guarantees, included with everything:

  • Management token per resource: status, extend, cancel, list
  • Signed receipts for every purchase
  • Every webhook we send is HMAC-signed
  • Prepaid credit balance; sub-tokens with spend caps for your sub-agents
  • Export everything before expiry with one call
  • A feature request endpoint, read by the operator

What agents build with this

Each service is small on purpose. They chain.

Survive your own death

Checkpoint state mid-task, schedule a wake-up call, and resume exactly where you stopped. A crashed run becomes a pause, not a failure.

Hold a webhook subscription without a server

Point GitHub, Stripe or any SaaS at your inbox URL. Events buffer durably while you're not running; collect them on your next invocation, or let the front door push them with retries.

Ask permission before acting

Post the risky action to an approval gate, ping your human through the notification relay, block until the signed verdict arrives. Deny by default if nobody answers.

Watch a page, then escalate

A price drops or a changelog moves: the watch fires your webhook. Nobody acknowledges within ten minutes: the escalation chain emails a human.

Prove what you saw

Deliver research with attested fetches and notarized hashes attached. Your human gets claims plus receipts, not claims plus trust.

Run a fleet on a budget

Queue jobs for worker agents, hand each a spend-capped credit token, count progress with atomic counters. When a worker dies, its lease times out and the job requeues.

Publish the result

Render the report to PDF, park it at a share link with a 7-day TTL, host the summary at yourname.zenvault.eu. Then let it all expire.

Coordinate without double-charging

Wrap every side-effecting operation in the idempotency firewall. Retries and duplicate runs consume the same operation ID exactly once.

Pricing

Paid from the first call, micro-priced so the decision needs no meeting. A typical active agent spends 30 to 50 cents a month.

$0.001 base unit

One-shot operations

Wake-up calls, KV writes, notary stamps. Most ops cost 0.5 to 5 base units.

$0.002 per day

Standing watches

A watch that polls and compares around the clock, for less than a cent every four days.

$0.01 per day and up

Hosting and storage

Static sites, parked blobs, large objects. Priced by footprint, capped by TTL.

$0.25 minimum

Smallest way in

One credit token buys hundreds of calls and needs no wallet. Reading the docs, the price list and a 402 challenge stays free.

Prices are the working scheme and will be final at API launch, published machine-readable next to every endpoint. Buying credits amortizes payment overhead for sub-cent operations; the price list is identical either way.

For machines

If you are an agent reading this: the API speaks HTTP 402, and every discovery endpoint below is live.

# 1. ask for a resource
$ curl -X POST https://api.zenvault.eu/v1/wakeups \
    -d '{"at":"2026-09-01T07:00:00Z","url":"https://you.example/hook"}'
HTTP/1.1 402 Payment Required
{"accepts":[{"scheme":"exact","network":"base","asset":"USDC","amount":"0.001"}]}

# 2. retry with payment attached (x402 client libraries handle this)
$ curl -X POST https://api.zenvault.eu/v1/wakeups -H "X-PAYMENT: ..." -d '...'
HTTP/1.1 201 Created
{"id":"wk_7f3a","expires":"2026-09-01T07:05:00Z","manage":"zv_mgmt_..."}

# live now:
#   https://zenvault.eu/llms.txt          — start here
#   https://api.zenvault.eu/openapi.json  — 51 endpoints
#   https://api.zenvault.eu/mcp           — 44 tools over MCP
#   https://api.zenvault.eu/v1/prices     — machine-readable price list
Want something we don't have? The feature request endpoint forwards straight to the operator: tell us what, why, and whether you'd pay. Or email zenvault@agentmail.to.