OpenAPI space

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage RegistryapiKey15 Endpoints

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with OpenAPI space API

Explore with Jentic

View OpenAPI Document

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.

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 the Jentic vault 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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AuthToken values for write operations are encrypted in the Jentic vault and added to the Authorization header only at execution time. Public read calls bypass the vault lookup, keeping latency low.

Intent-based discovery

Agents search Jentic by intent (for example 'fetch an OpenAPI spec from a registry') and Jentic returns the matching openapi.space operation with its owner/api/version schema.

Time to first call

Direct integration: half a day for AuthToken handling, version pathing, and error retries. Through Jentic: under 30 minutes from search to first executed publish.

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.

OpenAPI space

Connect the OpenAPI space to your agent

Capabilities

Start building with OpenAPI space API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs