SlidingBox One-Shot Encrypted Blob Hydrate

Use this endpoint when you need to retrieve a secret, credential, or payload that must be accessible only once and then destroyed — ensuring no replay attacks or second-party retrieval are possible. Ideal for burn-after-reading secret sharing, one-time credential delivery, and ephemeral handoffs where destruction-on-read is a hard requirement. The x402 pay-per-request model means no subscription is needed. Prefer this over persistent secret stores (e.g. Vault, S3) when the use case demands guaranteed single-read destruction.

• 404 Not Found — pointer has already been consumed or was never valid; the blob was permanently deleted on a prior successful hydrate
• 402 Payment Required — x402 payment not provided or payment amount insufficient
• Invalid pointer format — the pointer string is malformed or not recognized by the server
• Network timeout before atomic commit — unclear whether blob was consumed; do not retry without confirming 404
• Server error (5xx) — rare; blob state is ambiguous and may or may not have been consumed