Readme API Endpoints

Name: API Endpoints API
Brand: API Endpoints
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbasic31 EndpointsREST

Install Jentic One Beta

Connect the API Endpoints to your agent

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

Get metadata about the current project

uploadAPISpecification

updateAPISpecification

deleteAPISpecification

GET STARTED

Start building with API Endpoints API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically get metadata about the current project, uploadapispecification. Covers 31 operations with basic authentication.

Use for: I need to metadata about the current project, I want to uploadapispecification, Search for getapispecification, Find all updateapispecification

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

Use Cases

Patterns agents use API Endpoints API for, with concrete tasks.

★ E-Commerce Operations

Use the API Endpoints to perform e commerce operations programmatically. The API provides 31 endpoints covering core functionality including get metadata about the current project, uploadapispecification, getapispecification.

Call GET / to get metadata about the current project

Automated API Specification Management

Automate API specification operations by combining multiple API Endpoints endpoints. Agents can uploadapispecification and then getapispecification in a single workflow.

Call POST /api-specification to uploadapispecification, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Endpoints 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 basic tokens manually.

Search Jentic for 'get metadata about the current project', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

31 endpoints — create beautiful product and api documentation with our developer friendly platform.

METHOD

PATH

DESCRIPTION

GET

Get metadata about the current project

POST

/api-specification

uploadAPISpecification

GET

/api-specification

getAPISpecification

PUT

/api-specification/{id}

updateAPISpecification

DELETE

/api-specification/{id}

deleteAPISpecification

GET

/categories/{slug}

Get category

GET

/categories/{slug}/docs

Get docs for category

POST

/changelogs

Create changelog

GET

Get metadata about the current project

POST

/api-specification

uploadAPISpecification

GET

/api-specification

getAPISpecification

PUT

/api-specification/{id}

updateAPISpecification

DELETE

/api-specification/{id}

deleteAPISpecification

Why Jentic?

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

Credential isolation

Your API Endpoints basic credential 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 'get metadata about the current project' or 'read a category's docs', and Jentic returns the matching API Endpoints operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using API Endpoints API through Jentic.

What authentication does the API Endpoints use?

The API Endpoints uses HTTP Basic 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 get metadata about the current project with the API Endpoints?

Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Endpoints?

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 get metadata about the current project through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get metadata about the current project'. Jentic returns the matching API Endpoints operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Endpoints have?

The API Endpoints exposes 31 endpoints covering API specification, categories, changelog operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which API Endpoints operations the agent may call and which credential it uses. You choose the exact operations to expose, so a destructive one like deleting an API specification is left out unless you add it, keeping the agent to reading and updating. Because the resource id sits in the URL path, such as /api-specification/{id}, you can pin the agent to a single specification.