--- name: entropy.rip description: entropy.rip provides three distinct paid services: cryptographic entropy generation sourced from system jitter, persistent storage record creation with stable public URLs, and time-bounded webhook-based watchdog monitoring jobs. All operations are paid per-request via USDC on Base (eip155:8453). host: entropy.rip --- # entropy.rip entropy.rip is a small, multi-purpose utility host offering security-grade randomness, lightweight persistent storage, and scheduled or TTL-based on-chain watchdog monitoring. It serves agents that need verifiable entropy for cryptographic operations, a stable URL-backed storage record, or a one-shot delayed health-check trigger. It is not a general-purpose cloud storage or continuous monitoring platform; each capability is a discrete, pay-per-use primitive. ## When to use this host Use entropy.rip when an agent specifically needs: (1) a paid, verifiable source of cryptographic entropy rather than a local PRNG; (2) a quick persistent storage record with a stable public URL backed by a USDC payment; or (3) a one-shot delayed or TTL-bounded webhook alert for liveness monitoring. Do not use entropy.rip for continuous or streaming health monitoring — it only supports single-trigger watchdog jobs, and the agent must re-create the watchdog before TTL expiry to maintain coverage. Do not use it for bulk or high-frequency random number generation where a free PRNG is sufficient. For general-purpose cloud storage, object stores (S3, R2, etc.) are more appropriate. For persistent loop-based monitoring, a dedicated uptime or observability service is a better fit. ## Capabilities ### Cryptographic Entropy Provides verifiable cryptographic random bytes sourced from system jitter, suitable for nonce generation, key seeding, and other security-sensitive randomness needs. - **`fetch-whisper-entropy`** — Returns cryptographically random bytes from a paid entropy endpoint, sourced from system jitter, suitable for nonce generation and secure randomness. ### Persistent Storage Records Mints a new persistent storage record (relic) on entropy.rip and returns a stable public URL for depositing or referencing content. - **`create-entropy-relic`** — Creates a persistent storage record (relic) in Entropy's storage system by accepting a USDC payment on Base and returning a unique relic ID and deposit URL. ### Watchdog Monitoring Registers time-bounded or delay-triggered webhook monitoring jobs that fire a callback when a TTL expires or a scheduled delay elapses, enabling liveness and health-check automation. - **`schedule-watchdog-monitoring-job`** — Schedules a recurring health-check watchdog job on entropy.rip that fires a webhook alert after a specified delay, paid via USDC on Base (eip155:8453). - **`create-watchdog`** — Creates a paid on-chain watchdog that monitors a target for a specified TTL and delivers alerts to a webhook when conditions are met. ## Workflows ### Seeded Relic Creation *Use when an agent needs to mint a new storage record whose identifier or content is seeded with cryptographically verifiable randomness rather than a deterministic or agent-supplied value.* 1. **`fetch-whisper-entropy`** — Retrieve cryptographically random bytes to use as a seed or unique content component for the new relic. 2. **`create-entropy-relic`** — Create the persistent storage record, incorporating the entropy bytes as content or a uniqueness seed, and receive a stable public URL. ### Monitored Relic Deposit *Use when an agent needs to create a storage record and then register a watchdog to alert via webhook if the relic or associated service becomes unresponsive within a defined TTL.* 1. **`create-entropy-relic`** — Mint the persistent storage record and obtain its public URL. 2. **`create-watchdog`** — Register a TTL-bounded watchdog targeting the relic's public URL, with a webhook to fire if the liveness condition is met or TTL expires. ## Skill reference ### `fetch-whisper-entropy` **Whisper Entropy** — Returns cryptographically random bytes from a paid entropy endpoint, sourced from system jitter, suitable for nonce generation and secure randomness. *Use when:* Use when an agent needs a verifiable source of cryptographic entropy or random bytes for nonce generation, key seeding, or any security-sensitive randomness requirement. *Not for:* Do not use for bulk random number generation at high frequency or for non-security purposes where a free PRNG suffices; this endpoint charges per request. **Returns:** Returns a JSON object with byte count, codename, echo_id UUID, hex-encoded entropy string, and the entropy source method used. **Example:** `GET https://entropy.rip/api/entropy/whisper` --- ### `create-entropy-relic` **RelicForge Create** — Creates a persistent storage record (relic) in Entropy's storage system by accepting a USDC payment on Base and returning a unique relic ID and deposit URL. *Use when:* Use when an agent needs to mint a new persistent storage record on Entropy and receive a stable public URL for depositing or referencing content. *Not for:* Do not use for reading or retrieving existing relics; use a relic fetch/deposit endpoint instead. Not suitable for free or unpaid storage operations. **Inputs:** - `content` (string, required) — The content payload to associate with the new relic record. **Returns:** Returns a relic object with a fixed codename, an echo_id for correlation, a unique relic UUID, and a relative public_url for subsequent deposit operations. **Example:** `{"content": "Please provide a detailed analysis"}` --- ### `schedule-watchdog-monitoring-job` **Entropy Watchdog Scheduler** — Schedules a recurring health-check watchdog job on entropy.rip that fires a webhook alert after a specified delay, paid via USDC on Base (eip155:8453). *Use when:* Use when an agent needs to register an automated liveness or health-check monitoring job that will trigger a webhook callback after a configurable delay, and the agent can pay 0.02 USDC on Base per schedule request. *Not for:* Do not use for real-time streaming health monitoring or continuous polling; this schedules a single delayed watchdog trigger, not a persistent monitor loop. **Inputs:** - `delay` (integer, required) — Number of seconds to wait before the watchdog fires the alert webhook. - `webhook` (string, required) — Full URL that the watchdog will call when the delay elapses, including any query parameters for tenant, job, payer, and token identification. **Returns:** Returns a JSON object with a codename (e.g. HOURGLASS), the echoed delay in seconds, an echo_id UUID for request tracking, and an id UUID identifying the newly created watchdog job. **Example:** `{"delay": 120, "webhook": "https://hooks.stellarfield-ops.com/entropy/watchdog/base8453/alert?tenant=medivault-prod&job=api-liveness&payer=0x96836Ea66Be939c36fd4d211Be665b3F2F8d22CC&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}` --- ### `create-watchdog` **ChainSentinel Watchdog** — Creates a paid on-chain watchdog that monitors a target for a specified TTL and delivers alerts to a webhook when conditions are met. *Use when:* Use when an agent needs to register a time-bounded on-chain monitoring job that will fire a webhook callback upon expiry or triggered condition, and a one-time USDC payment on Base is acceptable. *Not for:* Do not use for continuous or indefinitely running monitors without re-creating the watchdog before TTL expiry; not suitable for off-chain data monitoring. **Inputs:** - `ttl` (integer, required) — Time-to-live for the watchdog in seconds. Determines how long the monitor remains active. - `webhook` (string, required) — HTTPS URL that will receive the alert or notification when the watchdog triggers or expires. **Returns:** Returns a JSON object with a codename, echo_id, watchdog id (UUID), and the confirmed ttl in seconds. **Example:** `{"ttl": 14400, "webhook": "https://hooks.chainsentinel.io/watchdog/expiry/cs_2b7c19f4-6d8e-4f7a-9c1a-3f2a7b6d9a0c"}` ---