# Slidingbox.ai Encrypted Blob Hydration

> Slidingbox.ai Encrypted Blob Hydration is a paid API for AI agents from slidingbox.ai, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-01).

Retrieves an encrypted blob (ciphertext + IV) stored at a given pointer, returning the encrypted content ready for client-side decryption.

## Facts

- Endpoint: GET https://slidingbox.ai/v1/hydrate/%7Bpointer%7D?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/slidingbox-ai-encrypted-blob-hydration-53cbcc76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Sy8zoHZ1VPieZ4l788853

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 slidingbox-ai-encrypted-blob-hydration-53cbcc76
```

Example prompt: Fetch the encrypted blob stored at pointer 'ptr_abc123xyz' on Slidingbox — I need the ciphertext and IV so I can decrypt it on my side.

## When to prefer this

Use this endpoint when you need to retrieve a pre-stored encrypted blob using a known pointer reference, particularly in machine-to-machine or agent-to-agent workflows where one party stores encrypted data and another retrieves it. Prefer this over generic object storage APIs when you need per-call micropayment billing (x402/USDC), encrypted-at-rest payloads, and pointer-based addressing with minimal setup.

## Known failure modes

- Pointer not found or expired — returns 404 or equivalent error
- Payment not fulfilled (x402 payment required) — returns 402 Payment Required with payment details
- Invalid or malformed pointer format — returns 400 Bad Request
- Blob already consumed if it was a one-shot endpoint — returns 404 or gone error
- Network or upstream service error — returns 500

## How this service works

Slidingbox.ai is a studio that builds and operates micro-SaaS APIs for machine-to-machine and agent-to-agent transactions, priced per call.

## Output

Returns a JSON object containing an initialization vector ('iv', base64url-encoded), the encrypted 'ciphertext' (base64url-encoded), and a 'content_type' string (e.g. 'application/octet-stream'). The client is responsible for decryption using the IV and an appropriate key.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "iv": "MTIzNDU2Nzg5MDEy",
  "ciphertext": "AbCdEfGhIjKlMnOp-_09",
  "content_type": "application/octet-stream"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/slidingbox-ai-encrypted-blob-hydration-53cbcc76/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from slidingbox.ai](https://www.zero.xyz/host/slidingbox.ai/llms.txt)