Install Jentic One Beta

Connect the Config API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Config 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%2Fswaggerhub.pailkun%2Fconfig-api" | 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%2Fswaggerhub.pailkun%2Fconfig-api" | 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 Config API.

create menu

all menus

menu by id

update menu by id

delete menu by id

Use Cases

Patterns agents use Config API for, with concrete tasks.

GET STARTED

Start building with Config API

Explore with Jentic One

View OpenAPI Document

Automated menu Management

Automate menu operations by combining multiple Config API endpoints. Agents can all menus and then menu by id in a single workflow.

Call GET /menu to all menus, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Config API 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 menu', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — global configuration store api.

METHOD

PATH

DESCRIPTION

POST

/menu

create menu

GET

/menu

all menus

GET

/menu/{id}

menu by id

PUT

/menu/{id}

update menu by id

DELETE

/menu/{id}

delete menu by id

POST

/project

create project

GET

/project

all projects

GET

/project/{code}

project by code

POST

/menu

create menu

GET

/menu

all menus

GET

/menu/{id}

menu by id

PUT

/menu/{id}

update menu by id

DELETE

/menu/{id}

delete menu by id

POST

/project

create project

GET

/project

all projects

GET

/project/{code}

project by code

Why Jentic?

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

Setup

Wiring the Config API by hand means pointing at its AWS eu-west-1 execution endpoint and calling its menu and project endpoints yourself. Through Jentic you install once, import Config API from the API Directory, store any connection detail once, and your agent calls it.

Permission scoping

Config API puts the menu and project id in the URL path (/menu/{id} and /project/{code}), so a rule can pin your agent to one menu or project. You choose the operations it may call, so it can stay on reading and creating entries while destructive ones like menu deletion are not included unless you add them.

Credential isolation

Any Config API connection detail 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 'create a menu' or 'get a project by code', and Jentic returns the matching Config API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 Config API through Jentic.

What authentication does the Config API use?

The Config API 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 menu with the Config API?

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

What are the rate limits for the Config API?

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 menu through Jentic?

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

How many endpoints does the Config API have?

The Config API exposes 20 endpoints covering menu, project, coordinate operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Config API operations and credentials the agent may use. You can allow it to read and create entries with GET /menu, GET /project, and POST /menu while leaving destructive calls like DELETE /menu/{id} out unless you add them. Since the menu and project identifiers sit in the URL path, such as /menu/{id} and /project/{code}, you can also pin the agent to a single menu or project.

Pailkun Config API

Name: Config API
Brand: Config API
Availability: InStock

Browse all Swaggerhub Pailkun APIs

Community OpenAPI document · agent-readyE CommerceStorefrontnone20 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create menu, all menus. Covers 20 operations.

Use for: I need to menu, I want to all menus, Search for menu by id, Find all menu by id

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

Global configuration store API. The API exposes 20 endpoints.

Jentic One on Github View OpenAPI Document