Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Spacebin, 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%2Fspaceb.in%2Fspaceb" | 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%2Fspaceb.in%2Fspaceb" | 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 Spacebin API.
Create a new document
Fetch a document by ID
Health check
Get instance configuration
Monitor Spacebin operational status and events
GET STARTED
Patterns agents use Spacebin API for, with concrete tasks.
★ Cloud Infrastructure Operations
Use the Spacebin to perform cloud infrastructure operations programmatically. The API provides 5 endpoints covering core functionality including create a new document, fetch a document by id, fetch raw plain text content of a document.
Call POST /api/ to create a new document
Automated Documents Management
Automate documents operations by combining multiple Spacebin endpoints. Agents can fetch a document by id and then fetch raw plain text content of a document in a single workflow.
Call GET /api/{documentId} to fetch a document by id, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Spacebin endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'create a new document', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — spacebin is a modern pastebin server.
METHOD
PATH
DESCRIPTION
/api/
Create a new document
/api/{documentId}
Fetch a document by ID
/api/{documentId}/raw
Fetch raw plain text content of a document
/ping
Health check
/config
Get instance configuration
/api/
Create a new document
/api/{documentId}
Fetch a document by ID
/api/{documentId}/raw
Fetch raw plain text content of a document
/ping
Health check
/config
Get instance configuration
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Spacebin by hand means reading its unauthenticated paste API, tracking the returned document id, and constructing the raw and lookup URLs yourself. Through Jentic you install once, import Spacebin from the API Directory, and your agent calls it.
Permission scoping
Spacebin needs no credential, so scoping is about operations: limit the agent to the operations it needs, such as creating a document or fetching one by id. You choose the operations it may call, so it only does what you allow and nothing more.
Credential isolation
Spacebin requires no credential, so there is no secret to store. Any configuration your Jentic One instance holds stays out of the agent's prompt, logs, and context.
Intent-based discovery
Agents search Jentic by intent such as 'create a new document' or 'fetch a paste as raw text', and Jentic returns the matching Spacebin 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 Spacebin API through Jentic.
What authentication does the Spacebin use?
The Spacebin uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a new document with the Spacebin?
Yes. Use the POST /api/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Spacebin?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new document through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new document'. Jentic returns the matching Spacebin operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Spacebin have?
The Spacebin exposes 5 endpoints covering documents, system operations.
Can I limit what my agent is allowed to do with the Spacebin API?
Yes. Because Spacebin needs no credential, scoping is about operations, and Jentic One is self-hosted by you, so your own rules decide which operations the agent may call. You can allow it to create a document with POST /api/ while blocking retrieval, or restrict it to fetching a document by id or its raw text and nothing more. The agent can only run the operations you permit.
For Agents
Programmatically create a new document, fetch a document by id. Covers 5 operations.
Use for: I need to a new document, I want to fetch a document by id, Search for fetch raw plain text content of a document, Find all health check
Not supported: Does not handle payments, communications, or crm - use for cloud infrastructure only.
Spacebin is a modern Pastebin server. The API allows creating and retrieving text documents (pastes). The API exposes 5 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>