# ENTROPY.RIP Relic Storage Retrieval

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

Retrieves a previously stored ephemeral data relic from ENTROPY.RIP's cryptographic storage by its unique ID

## Facts

- Endpoint: GET https://entropy.rip/api/storage/relic/retrieve/%7Bid%7D
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/entropy-rip-relic-storage-retrieval-5775092c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bQXFL47aPPH1-qPJYSGal

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-relic-storage-retrieval-5775092c
```

Example prompt: Retrieve the stored relic with ID abc123 from entropy.rip's ephemeral storage and show me its contents.

## When to prefer this

Use this endpoint when an AI agent or automated process needs to retrieve a specific piece of data that was previously stored in ENTROPY.RIP's ephemeral storage system. Prefer this over general-purpose storage APIs when operating within the ENTROPY.RIP agent infrastructure ecosystem, especially when the stored content is tied to dead man's switches, proofs of existence, or agent-to-agent data passing workflows.

## Known failure modes

- Relic ID not found or expired — returns 404 or empty content if the ID was never stored or has been purged
- Invalid ID format — malformed ID path parameter may result in a 400 or 422 error
- Payment failure — x402 payment of $0.05 USDC not completed, resulting in 402 Payment Required
- Relic already consumed — ephemeral relics may be single-use and return an error if previously retrieved
- Service unavailable — entropy.rip infrastructure down, returning 500 or timeout

## How this service works

A suite of survival tools for autonomous AI agents. Residential proxies, dead man's switches, ephemeral storage, and cryptographic proofs of existence.

## Output

Returns a JSON object containing the stored relic's content (the original data payload) and a codename field labeled 'RELIC', confirming successful retrieval of the ephemeral storage item associated with the given ID.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "content": "...",
  "codename": "RELIC"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/entropy-rip-relic-storage-retrieval-5775092c/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)