Install Jentic One Beta

Connect the OpenAPI space to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenAPI space, 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%2Fopenapi.space%2Fopenapi-space" | 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%2Fopenapi.space%2Fopenapi-space" | 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 OpenAPI space API.

List all owners that have published an API on openapi.space

Retrieve every API published by a specific owner, with version history

Publish a new version of an API spec under an existing owner/api path

Fetch the swagger.json for a specific version of a published API

Fork an existing API into your own namespace to maintain a derived spec

GET STARTED

Start building with OpenAPI space API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OpenAPI space API for, with concrete tasks.

★ Internal API Catalog Sync

Mirror an organisation's internal OpenAPI specs into openapi.space so teams can browse and consume them through a shared registry. A scheduled job lists every API per owner, compares against the source repo, and PUTs new versions when the upstream spec changes. Header-based AuthToken keeps writes scoped to the publishing service account.

POST the latest swagger.json to /apis/{owner}/{api}/{version} after each release tag, then verify with GET /apis/{owner}/{api} that the version appears in the version list.

Spec Discovery for Integration Engineering

Power an internal search tool that lets integration engineers discover candidate APIs by browsing owners and APIs on openapi.space. The agent enumerates owners with GET /apis, fans out to GET /apis/{owner}, and indexes resulting metadata into the search backend. Public read endpoints make this loop quota-friendly.

Walk every owner returned by GET /apis, expand each with GET /apis/{owner}, and write the resulting (owner, API, version) triples into the search index.

Community-Driven Spec Improvement

Forks and ratings let an agent maintain a community-improved fork of a published spec while leaving the upstream untouched. Engineers fork the API into their owner namespace, push fixes, and a separate scheduled job rates the original to flag widely-forked specs for upstream attention.

POST to fork the upstream API into the user's owner namespace, then publish the corrected swagger.json under /apis/{user}/{api}/{version}.

AI Agent Spec Lookup via Jentic

Give an AI agent the ability to fetch an OpenAPI spec by owner and API name through Jentic. The agent searches Jentic by intent, loads the schema for the swagger.json retrieval endpoint, and executes with the owner/api/version triple. The AuthToken is held in your Jentic One instance for write actions and never leaves it.

Use Jentic search 'fetch an OpenAPI spec from a registry', load the GET /apis/{owner}/{api}/{version}/swagger.json schema, and execute with owner, API, and version values.

Key Endpoints

15 endpoints — openapi space is a registry for sharing and versioning openapi specifications, exposing 15 endpoints to list, publish, version, fork, and rate api documents.

METHOD

PATH

DESCRIPTION

GET

/apis

List all owners on the registry

GET

/apis/{owner}

List APIs published by an owner

GET

/apis/{owner}/{api}

Retrieve metadata for an API

POST

/apis/{owner}/{api}/{version}

Publish a new version

GET

/apis/{owner}/{api}/{version}/swagger.json

Fetch swagger.json for a version

DELETE

/apis/{owner}/{api}/{version}

Delete a version

DELETE

/apis/{owner}/{api}

Delete an API

GET

/apis

List all owners on the registry

GET

/apis/{owner}

List APIs published by an owner

GET

/apis/{owner}/{api}

Retrieve metadata for an API

POST

/apis/{owner}/{api}/{version}

Publish a new version

GET

/apis/{owner}/{api}/{version}/swagger.json

Fetch swagger.json for a version

DELETE

/apis/{owner}/{api}/{version}

Delete a version

DELETE

/apis/{owner}/{api}

Delete an API

Why Jentic?

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

Setup

Wiring the OpenAPI space API by hand means setting the Authorization header with your token and handling the owner, API, and version path conventions yourself. Through Jentic you install once, import the OpenAPI space API from the API Directory, store the token once, and your agent calls it.

Permission scoping

OpenAPI space puts the owner, API, and version in the URL path (/apis/{owner}/{api}/{version}), so a rule can pin your agent to one owner or API for read access. You choose the operations it may call, so publishing a version or deleting one are not included unless you add them.

Credential isolation

Your OpenAPI space token 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 'list APIs published by an owner' or 'fetch the swagger for a version', and Jentic returns the matching OpenAPI space operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using OpenAPI space API through Jentic.

What authentication does the OpenAPI space API use?

Write endpoints require an AuthToken passed in the Authorization header (apiKey scheme). Most read endpoints under /apis are public. Through Jentic the AuthToken is stored encrypted in the vault and attached to outbound calls only when the operation requires it.

Can I publish a new version of a spec to OpenAPI space?

Yes. POST your swagger.json to /apis/{owner}/{api}/{version} with the AuthToken header. The registry stores the version and exposes it via GET /apis/{owner}/{api}/{version}/swagger.json for any consumer.

What are the rate limits for the OpenAPI space API?

The hosted spec does not document explicit rate limits. As a community registry, batched reads are encouraged; if you need high-volume mirroring of all owners and APIs, throttle to a few requests per second and cache responses locally.

How do I retrieve a swagger.json by owner and API through Jentic?

Run the Jentic search 'fetch an OpenAPI spec from a registry', select GET /apis/{owner}/{api}/{version}/swagger.json, load the schema, and execute with the owner, API, and version values. The structured response is the swagger.json document itself.

Can I fork an API on openapi.space?

Yes. The registry supports forking an existing API into your own owner namespace so you can maintain a derived spec. After forking, publish updates with POST /apis/{owner}/{api}/{version} as you would for any other API.

How do I delete a deprecated API version?

Call DELETE /apis/{owner}/{api}/{version} with a valid AuthToken. To remove every version of an API at once, call DELETE /apis/{owner}/{api}. Both calls require the AuthToken to belong to the owner of the API.

Can I limit what my agent is allowed to do with the OpenAPI space API?

Yes. Jentic One is self-hosted, so you run it yourself and your own rules decide which OpenAPI space operations and credentials the agent may use. Because the registry puts the owner, API, and version in the URL path, you can pin the agent to read-only calls like GET /apis/{owner} or a single owner's specs while withholding write operations. Publishing a version with POST /apis/{owner}/{api}/{version} or removing one with DELETE /apis/{owner}/{api}/{version} is only available if you explicitly grant it, and your AuthToken stays inside your own instance.

OpenAPI space

Name: OpenAPI space API
Brand: OpenAPI space
Availability: InStock

Browse all Openapi Space APIs

Community OpenAPI document · agent-readyDeveloper ToolsPackage RegistryapiKey15 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List, publish, version, fork, and rate OpenAPI specifications hosted in the openapi.space registry through 15 endpoints, with public reads and token-authenticated writes.

Use for: Publish a new version of an API spec, List all APIs owned by a specific user, Retrieve the swagger.json for a given API version, Fork an API into my own namespace

Not supported: Does not generate code, lint specs, or run mock servers - use for OpenAPI spec hosting, versioning, and discovery only.

OpenAPI space is a registry for sharing and versioning OpenAPI specifications, exposing 15 endpoints to list, publish, version, fork, and rate API documents. Owners and APIs are first-class resources, so an agent can browse all specs published by a user, retrieve a specific version's swagger.json, or open issues against a given API. The service uses a header-based AuthToken for write operations while most read calls are public. It is well suited to tooling that catalogs internal APIs or syndicates specs across teams.

Jentic One on Github View OpenAPI Document

Connect the OpenAPI space to your agent

Capabilities

Start building with OpenAPI space API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OpenAPI space