Back to Browse
PayPerWork Box Key-Value Store (PUT)
x402
PayPerWork Box Key-Value Store (PUT) is a paid API for AI agents from payperwork.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-02).
Stores an arbitrary JSON/form/text payload under a named key within a specified box (wallet box, channel, or 'me'), with a configurable TTL.
Price / call$0.002
Success—
StatusUnknown
How this service works
Store the request body under {key} in box {box} (a box_ id, a channel name, or "me" for your wallet's box). Query ttl=seconds (60 to 604800, default 3600). Body up to 65536 bytes.
Output
Returns a confirmation that the payload has been stored, along with metadata such as the box ID, key name, and the sequence number for the write — which can be used with the corresponding GET or block-wait endpoint to retrieve or monitor the value.
Example use cases
Agent workflow state handoff
“Store the current workflow state {"step": 3, "context": "approved"} under the key 'workflow-state' in box 'box_abc123' so the next agent step can pick it up — keep it for 3600 seconds.”
Shared channel data drop
“Write this report summary {"report": "Q2 sales up 12%"} to key 'q2-report' in the channel box 'sales-team', and make it expire after 86400 seconds.”
Personal wallet box cache
“Save my user preferences {"theme": "dark", "lang": "en"} under the key 'user-prefs' in my own box (use 'me') with a TTL of 604800 seconds.”
Technical details
Endpoint
PUThttps://payperwork.app/box/:box/:key?utm_source=zero.xyzWhen to prefer
Choose this endpoint when an AI agent needs to persist ephemeral state, share data between agent steps or agents via a named box, or cache intermediate results with a TTL. It is purpose-built for agentic workflows where data needs to be readable by key later (via a sibling GET or block-wait endpoint). Prefer this over generic object storage when you need tight TTL control (60s–7 days), per-call micropayment pricing via x402, and native compatibility with the payperwork.app agent ecosystem.
Side effects
- Body exceeds 65536 bytes — request rejected with payload-too-large error
- TTL outside 60–604800 range — rejected with invalid parameter error
- Invalid or inaccessible box ID — returns 404 or authorization error
- Malformed key name — rejected with bad request error
- Payment failure (x402 protocol) — returns 402 Payment Required
- Rate limiting — returns 429 Too Many Requests
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"