Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pinnwand 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%2Fpinnwand.readthedocs.io%2Fpinnwand" | shStep 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%2Fpinnwand.readthedocs.io%2Fpinnwand" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Pinnwand API.
Create text pastes with syntax highlighting via the JSON API endpoint
Post pastes through a curl-compatible interface for command-line usage
Retrieve raw paste content by unique identifier
Remove pastes using secure deletion tokens
Share code snippets with generated URLs for collaboration
GET STARTED
Patterns agents use Pinnwand API for, with concrete tasks.
★ Code Snippet Sharing
Share code snippets and configuration files by creating pastes through the Pinnwand API. The /api/v1/paste endpoint accepts text content with optional syntax highlighting and returns a shareable URL. Developers use this for sharing error logs, config snippets, and code examples during debugging and collaboration.
Create a paste with a Python code snippet of 20 lines and retrieve the shareable URL
Automated Log and Output Capture
Capture command output, build logs, or error traces by posting them to Pinnwand automatically. The /curl endpoint accepts text from command-line pipes, making it simple to integrate into shell scripts and CI/CD pipelines for preserving transient output.
Post a build error log to the /curl endpoint and retrieve the URL for sharing with the team
Temporary Content Storage
Store text content temporarily with the ability to delete it later using a secure token. Pinnwand pastes serve as lightweight temporary storage for text data that needs to be shared briefly and then removed, without requiring database setup or cloud storage configuration.
Create a paste with sensitive configuration data, share the URL, then remove it using the deletion token
AI Agent Content Sharing
AI agents use the Pinnwand API through Jentic to create and manage pastes for sharing generated content, code outputs, or diagnostic information. Agents search for paste operations by intent and execute calls without authentication since the API is public.
Search Jentic for 'create a code paste', load the Pinnwand /api/v1/paste endpoint schema, and create a paste with generated code output
4 endpoints — jentic publishes the only available openapi specification for pinnwand api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/api/v1/paste
Create a new paste via JSON API
/curl
Create a paste via curl-friendly interface
/raw/{id}
Retrieve raw paste content
/remove/{token}
Remove a paste by deletion token
/api/v1/paste
Create a new paste via JSON API
/curl
Create a paste via curl-friendly interface
/raw/{id}
Retrieve raw paste content
/remove/{token}
Remove a paste by deletion token
What agents get from Jentic-routed access to this vendor.
Setup
Pinnwand needs no authentication, so wiring it by hand still means managing the paste-create call, tracking the deletion token it returns, and handling retries yourself. Through Jentic you install once, import Pinnwand from the API Directory, and your agent calls it.
Permission scoping
You limit the agent to the operations it needs, such as creating a paste or reading a raw paste. Because you choose the allowed operations, paste removal stays out of scope unless you add it.
Credential isolation
Pinnwand needs no credential, so there is none to store; any deletion token returned by a paste is held 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 code paste' or 'fetch a raw paste', and Jentic returns the matching Pinnwand operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Pinnwand API through Jentic.
Why is there no official OpenAPI spec for Pinnwand API?
Pinnwand does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pinnwand 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 Pinnwand API use?
The Pinnwand API does not require authentication. It is a public pastebin service where anyone can create, read, and delete pastes. Deletion requires the unique token returned when a paste is created.
Can I create pastes with syntax highlighting?
Yes. The POST /api/v1/paste endpoint accepts a lexer parameter that specifies the programming language for syntax highlighting. The paste is then rendered with appropriate highlighting when viewed in a browser.
How do I delete a paste after sharing it?
When you create a paste, the API returns a removal token. Use GET /remove/{token} with that token to permanently delete the paste. Store the token securely if you plan to remove the paste later.
How do I create a paste through Pinnwand using Jentic?
Search Jentic for 'create a code paste', load the /api/v1/paste operation schema, and execute with your text content and optional lexer parameter. No authentication is needed. Jentic returns the paste URL and deletion token.
What is the difference between the /api/v1/paste and /curl endpoints?
POST /api/v1/paste accepts structured JSON with content, lexer, and expiry fields. POST /curl accepts plain text body directly, designed for piping command output (e.g., 'cat file.py | curl -X POST -d @- https://bpaste.net/curl'). Both create pastes but /curl is optimized for shell usage.
Can I limit what my agent is allowed to do with the Pinnwand API?
Yes. Because Jentic One runs self-hosted on your own instance, your rules decide which Pinnwand operations the agent may call. You can allow it to create a paste through POST /api/v1/paste or read a raw paste through GET /raw/{id} while keeping paste removal via GET /remove/{token} out of scope. Removal only becomes available if you explicitly add it to the allowed operations.
Know of an official OpenAPI document? Contribute it →
For Agents
Create, retrieve, and delete text pastes for sharing code snippets and text content programmatically through a pastebin service.
Use for: I need to create a paste with a code snippet, I want to retrieve the raw content of a paste, Remove a paste using its deletion token, Share a text snippet via a pastebin URL
Not supported: Does not handle version control, code review, or file storage - use for ephemeral text paste sharing only.
Jentic publishes the only available OpenAPI specification for Pinnwand API, keeping it validated and agent-ready. Pinnwand API is a pastebin service that enables creating, retrieving, and removing text pastes programmatically. The API supports posting code snippets and text content via both a structured JSON endpoint and a curl-friendly interface, retrieving raw paste content by ID, and removing pastes with deletion tokens across 4 endpoints.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>