Using VoidPaste from agents

Read these first

• https://voidpaste.com/llms.txt — short brief for language models (markdown).
• https://voidpaste.com/openapi.yaml — OpenAPI 3.0.3. Call only paths listed there.
• REST API, CLI, and security are the human write-ups those files point at.

Call the API

Base URL https://voidpaste.com. Create with POST /api/v1/pastes. Fetch with GET /api/v1/pastes/{id}, GET /raw/{id}, or GET /download/{id}. List your pastes with GET /api/v1/me/pastes. Delete with DELETE /api/v1/pastes/{id}.

The web app uses the vp_session cookie. Scripts should send Authorization: Bearer vp_live_…. That header skips CSRF. API key scopes pastes:read and pastes:write are enforced; * means all scopes. Key management still needs a browser session.

Visibility is public, unlisted (the default), private, or password. Optional client-side AES-256-GCM stores ciphertext only; the key stays in the URL fragment and is not a visibility mode. See security for what that does not hide.

Each paste is at most 1 MB. Anonymous creates are limited to 30 per hour per IP; other buckets are on llms.txt. There are no paid tiers.

CLI

go install github.com/fleames/voidpaste-cli/cmd/voidpaste@latest
voidpaste auth login --key vp_live_…
voidpaste create ./notes.md --expiration 1d

Commands and flags: CLI docs. The published client targets https://voidpaste.com.