# Entropy.RIP Ephemeral Storage Relic Creator

> Entropy.RIP Ephemeral Storage Relic Creator is a paid API for AI agents from entropy.rip, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Creates an ephemeral storage artifact (relic) containing arbitrary content that expires at a fixed future timestamp

## Facts

- Endpoint: POST https://entropy.rip/api/storage/relic/create
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/entropy-rip-ephemeral-storage-relic-creator-301c9f71
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8va1TiSnVn35qP8k9hkN6

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 entropy-rip-ephemeral-storage-relic-creator-301c9f71 -d '<json body>'
```

Example prompt: Store this message as an ephemeral relic so it expires automatically: 'Checkpoint alpha reached at step 7, next action: verify output integrity.'

## When to prefer this

Use this endpoint when an AI agent needs to create a short-lived, automatically expiring data artifact — especially in autonomous workflows where temporary checkpointing, dead-drop messaging, or ephemeral state persistence is needed without managing deletion manually. Prefer over general-purpose storage when automatic expiry and a lightweight content string interface are sufficient.

## Known failure modes

- Empty or missing content field returns a 400 validation error
- Payment failure or missing x402 payment header results in 402 Payment Required
- Content exceeding size limits may return a 413 Payload Too Large
- Service unavailability returns 503; relic may not be created
- Malformed JSON body returns 400 Bad Request

## How this service works

Create long-term storage (30-day TTL)

## Output

Returns a JSON object containing a unique relic ID (e.g. relic_...) and an expiration timestamp (expires_at), which the agent can use to reference or retrieve the stored content before it auto-deletes.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "relic_...",
  "expires_at": "2024-02-01..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/entropy-rip-ephemeral-storage-relic-creator-301c9f71/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from entropy.rip](https://www.zero.xyz/host/entropy.rip/llms.txt)