canonical: https://jentic.com/apis/paste.monster/paste-monster

# Paste Monster API

Jentic publishes the only available OpenAPI specification for Paste Monster API, keeping it validated and agent-ready. The Paste Monster API provides full CRUD operations for a pastebin service, allowing authenticated users to create, read, edit, and delete text pastes. It includes 5 endpoints covering paste creation, retrieval by ID, content editing, deletion, and user profile access via API key authentication in the Authorization header.

## For AI agents

Create, read, edit, and delete text pastes on Paste Monster with API key authentication. Retrieve user profile information and manage paste lifecycle.

## Scope

Does not handle syntax highlighting selection, paste expiry, or collaborative editing - use for basic text paste CRUD with API key authentication only.

## Capabilities

- Create new text pastes with content and metadata
- Retrieve paste content by unique paste identifier
- Edit existing paste content after creation
- Delete pastes permanently via authenticated requests
- Access authenticated user profile and paste history

## Use cases

### Authenticated Paste Management

Create and manage text pastes with full lifecycle control using API key authentication. Unlike anonymous pastebin services, Paste Monster ties pastes to your account, enabling editing and deletion after creation. The Authorization header carries your API key for all write operations, ensuring only paste owners can modify or remove content.

Example prompt: Create a new paste via POST /create with content in the request body, then edit it via PATCH `/edit/{pasteId}` with updated content

### Temporary Code Sharing with Cleanup

Share code snippets or configuration files temporarily and clean them up when no longer needed. The Paste Monster API lets you create a paste, share the URL, and then delete it via DELETE `/delete/{pasteId}` when the recipient has retrieved the content. This supports workflows where sensitive configuration should not persist indefinitely on public services.

Example prompt: Create a paste containing database credentials via POST /create, share the paste ID with the recipient, then delete via DELETE `/delete/{pasteId}` after confirmation

### Developer Paste History Tracking

Access your user profile and paste history through the /@me endpoint to audit previously created pastes. This enables automation tools to track which pastes have been shared, identify stale content for cleanup, or build personal snippet libraries from your paste history.

Example prompt: Retrieve user profile and paste history via GET /@me to list all pastes created with this API key

### AI Agent Paste Operations via Jentic

AI agents create, edit, and delete pastes through Jentic without managing API key headers directly. Jentic stores the Authorization header value securely and provides operation discovery, letting agents perform paste lifecycle operations by describing their intent rather than constructing raw HTTP requests.

Example prompt: Search Jentic for 'create a text paste', load the Paste Monster create operation schema, and execute with content payload using stored API key credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/create` | Create a new paste |
| GET | `/paste/@{pasteId}` | Retrieve a paste by ID |
| PATCH | `/edit/{pasteId}` | Edit an existing paste |
| DELETE | `/delete/{pasteId}` | Delete a paste permanently |
| GET | `/@me` | Get user profile and paste history |

## Key resources

- **Pastes** — Create, retrieve, edit, and delete text paste entries
- **Users** — Access authenticated user profile and paste history

## Why Jentic

- **Setup:** Wiring the Paste Monster API by hand means learning its API key auth in the Authorization header, setting the paste.monster/api host, and building request shaping for paste ids yourself. Through Jentic you install once, import Paste Monster from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Paste Monster puts the paste id in the URL path (/paste/@{pasteId}, `/edit/{pasteId}`), so a rule can pin your agent to one paste for reads and edits. You choose the operations it may call, so destructive ones like deleting a paste are not included unless you add them.
- **Credential handling:** Your Paste Monster API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a text paste' or 'edit an existing paste', and Jentic returns the matching Paste Monster operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pastebin API** — Largest general-purpose pastebin with expiry settings and visibility controls
- **CentOS Pastebin API** — Unauthenticated community pastebin with trending and recent feeds
- **Pastery API** — Clean minimalist pastebin with list, create, and delete operations
- **GitHub API** — Source control platform with Gists for versioned code sharing

## FAQ

### Why is there no official OpenAPI spec for Paste Monster API?

Paste Monster does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Paste Monster API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Paste Monster API use?

The API uses an API key passed in the Authorization header for all operations. Through Jentic, the API key is stored encrypted in the credential vault and agents authenticate without exposing the key in their context.

### Can I edit a paste after creating it?

Yes. Use PATCH `/edit/{pasteId}` with the updated content in the request body. You must authenticate with the same API key used to create the paste. Only paste owners can edit their content.

### How do I delete a paste?

Call DELETE `/delete/{pasteId}` with your API key in the Authorization header. The paste is permanently removed. Only the paste creator can delete it.

### How do I retrieve my paste history?

Call GET /@me with your API key in the Authorization header. The endpoint returns your user profile along with your paste history, including paste IDs and creation timestamps.

### How do I manage pastes through Jentic?

Search Jentic for 'edit a text paste' or 'delete a paste' to find the corresponding Paste Monster operations. Load the schema to see required parameters (paste ID, content), then execute with your stored credentials. Install with pip install jentic.

### Can I limit what my agent is allowed to do with the Paste Monster API?

Yes. Because you run Jentic One yourself, your own rules decide which Paste Monster operations the agent can call, so you can allow reads and edits like GET /paste/@{pasteId} and PATCH `/edit/{pasteId}` while leaving out destructive ones such as DELETE `/delete/{pasteId}.` Since the paste ID sits in the URL path, a rule can pin the agent to a single paste for retrieval and editing. Your API key is stored by your own instance and injected at execution time, so the agent only calls the endpoints you have permitted.