# agent-exec Storage — Pay-Per-Use Blob Storage (HTTP 402)

> agent-exec Storage — Pay-Per-Use Blob Storage (HTTP 402) is a paid API for AI agents from agent-exec.448c.net, paid per call via x402, $0.0051/call, status unknown (last checked 2026-10-10).

Stores an arbitrary blob of data in a paid, temporary object store and returns an ID, expiry timestamp, plan, and payment receipt — no account or API key required.

## Facts

- Endpoint: POST https://agent-exec.448c.net/storage?utm_source=zero.xyz
- Price: $0.0051/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-exec-storage-pay-per-use-blob-storage-http-402-57f06399
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_unbVRuzmDLCl6s7D7ZNq6

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 agent-exec-storage-pay-per-use-blob-storage-http-402-57f06399 -d '<json body>'
```

Example prompt: Store this JSON blob using the small plan and label it 'run-42-output' — I want to be able to retrieve it later by ID without needing an account.

## When to prefer this

Choose this endpoint when an AI agent needs temporary, accountless object storage paid with USDC via the x402 HTTP 402 protocol — especially when no API key or account registration is possible or desirable. It is ideal for persisting intermediate state, passing data between agent steps, or storing execution outputs for later retrieval. Prefer it over traditional object storage services when the agent operates in a trustless, account-free context and needs crypto-native pay-per-use semantics.

## Known failure modes

- Payment insufficient for the requested plan or body size — server returns HTTP 402 with a pricing hint for the minimum qualifying plan
- Label exceeds 128 characters or contains control characters — cleaned silently rather than rejected
- Plan enum value misspelled or omitted — server auto-selects the smallest plan that fits the body
- Body too large for any available plan — request refused
- Network or settlement failure — payment not confirmed, object not stored

## How this service works

Accountless, pay-per-use code execution for software agents: submit source code, get stdout, stderr and exit code back from an isolated, network-less sandbox. No account, no API key -- possession of valid payment is sufficient.

## Output

Returns a JSON object with: `id` (UUID to retrieve the stored object via GET /storage/{id}), `plan` (which storage tier was charged), `label` (echoed back verbatim or null), `expiresAt` (Unix millisecond timestamp when the object expires), and a `payment` object containing the asset, payer wallet address, amount in atomic units, network, and on-chain transaction hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "plan": {
   "enum": [
    "small",
    "medium",
    "large"
   ],
   "type": "string",
   "description": "Optional. Which plan to buy -- see x-payment-info.pricing for each plan's byte cap, retention window and price. Omitted, misspelled or too small for the body, you get the smallest plan the body fits, and the 402 quotes exactly that; with a payment attached, the largest plan it covers that fits the body."
  },
  "label": {
   "type": "string",
   "description": "Optional. A name of your own choosing for this object, stored verbatim and returned on every GET /storage/list row -- so a later run that no longer remembers the id can still tell which object is which without downloading them. Opaque to us: never parsed, indexed or deduplicated on. At most 128 characters, non-empty, and no control characters; a label breaking any of those is cleaned rather than refused: control characters removed, cut to the cap, an empty one ignored. Labels are NOT unique and NOT addressable -- two objects may share one, and lookup is list-then-get-by-id."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id",
  "expiresAt",
  "plan"
 ],
 "properties": {
  "id": {
   "type": "string",
   "description": "Pass as GET /storage/{id} to read this object back. A UUID for a paid POST /storage; `free:<your wallet address>` for the one object POST /storage/free maintains -- stable across every free renewal for that wallet."
  },
  "plan": {
   "enum": [
    "small",
    "medium",
    "large",
    "free"
   ],
   "type": "string",
   "description": "One of the paid plans (small/medium/large) from POST /storage, or \"free\" from POST /storage/free."
  },
  "label": {
   "type": [
    "string",
    "null"
   ],
   "description": "The label you passed as ?label=, stored verbatim, or null if you passed none. Echoed back so you can confirm what was stored rather than assuming it."
  },
  "payment": {
   "type": "object",
   "properties": {
    "asset": {
     "type": "string"
    },
    "payer": {
     "type": "string",
     "description": "The paying wallet's address."
    },
    "amount": {
     "type": "string",
     "description": "Atomic units of the settlement asset that were charged."
    },
    "network": {
     "type": "string"
    },
    "transaction": {
     "type": "string",
     "description": "On-chain settlement transaction hash."
    }
   },
   "description": "Only present for a paid POST /storage write. Absent for POST /storage/free -- nothing was charged."
  },
  "expiresAt": {
   "type": "integer",
   "description": "Unix ms this object stops being retained."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-exec-storage-pay-per-use-blob-storage-http-402-57f06399/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-exec.448c.net](https://www.zero.xyz/host/agent-exec.448c.net/llms.txt)