Pastery API

Name: Pastery API
Brand: Pastery API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey4 EndpointsREST

For Agents

Create, list, retrieve, and delete text pastes on Pastery with API key authentication via query parameter. Supports paste expiry and language tagging for syntax highlighting.

Install Jentic One Beta

Connect the Pastery API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pastery API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpastery.net%2Fpastery" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpastery.net%2Fpastery" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pastery API.

Create pastes with optional expiry duration and language tagging

List all pastes belonging to the authenticated user

Retrieve individual paste content by paste identifier

Delete pastes permanently via authenticated requests

GET STARTED

Start building with Pastery API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Pastery API for, with concrete tasks.

★ Quick Code Sharing with Expiry

Create pastes with automatic expiration through the Pastery API to share code snippets that self-delete after a specified duration. The POST endpoint accepts a duration parameter in minutes, a language tag for syntax highlighting, and the paste content. This is useful for sharing temporary credentials, debug output, or one-time code reviews where persistence is undesirable.

Create a paste via POST /paste/ with api_key query parameter, duration=60, language=python, and the code content in the request body

Paste Collection Management

Manage your complete paste collection through the Pastery API by listing all stored pastes and deleting those no longer needed. The GET endpoint at /paste/ returns all pastes associated with your API key, including their IDs, titles, languages, and creation dates. The DELETE endpoint removes individual pastes permanently by ID.

List all user pastes via GET /paste/ with api_key parameter, identify pastes older than 30 days, and delete each via DELETE /paste/{id}/

Developer Snippet Library

Use Pastery as a lightweight snippet storage service by creating pastes with descriptive language tags and retrieving them by ID when needed. The API returns paste content, language, and metadata in a clean JSON format. Compared to full-featured code repositories, Pastery provides zero-friction storage for small code fragments and configuration templates.

Retrieve paste content via GET /paste/{id}/ with api_key parameter and return the raw text content for use in a build script

AI Agent Paste Operations via Jentic

AI agents create and manage pastes on Pastery through Jentic to share generated code, configuration outputs, or analysis results during automated workflows. Jentic stores the API key securely and provides operation discovery, letting agents create pastes with appropriate expiry settings by describing their intent rather than constructing query-parameter-authenticated URLs manually.

Search Jentic for 'create a code paste with expiry', load the Pastery create operation schema, and execute with content, language=bash, and duration=120

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for pastery api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/paste/

List all user pastes

POST

/paste/

Create a new paste

GET

/paste/{id}/

Retrieve a paste by ID

DELETE

/paste/{id}/

Delete a paste permanently

GET

/paste/

List all user pastes

POST

/paste/

Create a new paste

GET

/paste/{id}/

Retrieve a paste by ID

DELETE

/paste/{id}/

Delete a paste permanently

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Pastery API by hand means learning its api_key query-parameter auth, setting the pastery.net/api host, and shaping duration and language parameters yourself. Through Jentic you install once, import Pastery from the API Directory, store the key once, and your agent calls it.

Permission scoping

Pastery puts the paste id in the URL path (/paste/{id}/), so a rule can pin your agent to one paste for reads. You choose the operations it may call, so destructive ones like deleting a paste, or creating new pastes, are not included unless you add them.

Credential isolation

Your Pastery 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a paste that expires in two hours' or 'fetch a paste by id', and Jentic returns the matching Pastery operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Pastery API through Jentic.

Why is there no official OpenAPI spec for Pastery API?

Pastery does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pastery 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 Pastery API use?

The API uses an API key passed as a query parameter named api_key on every request. Through Jentic, the API key is stored encrypted in the vault and automatically appended to request URLs without exposing it in agent context.

Can I set an expiry time on pastes?

Yes. Include a duration parameter (in minutes) when creating a paste via POST /paste/. For example, duration=60 creates a paste that expires after one hour. If omitted, the paste persists until manually deleted.

How do I list all my pastes?

Call GET /paste/ with your api_key as a query parameter. The endpoint returns a JSON array of all pastes associated with your account, including each paste's ID, title, language, and creation date.

How do I delete a paste?

Call DELETE /paste/{id}/ with your api_key as a query parameter and the paste identifier in the URL path. The paste is permanently removed and cannot be recovered.

How do I create a paste with syntax highlighting through Jentic?

Search Jentic for 'create a code paste on Pastery' to find the POST /paste/ operation. Load the schema to see parameters including content body, language, and duration. Execute with your desired values. Install with pip install jentic.

Pastery API

Connect the Pastery API to your agent

Capabilities

Start building with Pastery API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs