Config API

Name: Config API API
Brand: Config API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontnone20 EndpointsREST

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

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.

Install Jentic One Beta (Self-Hosted)

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

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

create menu

all menus

menu by id

update menu by id

delete menu by id

GET STARTED

Start building with Config API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ E-Commerce Operations

Use the Config API to perform e commerce operations programmatically. The API provides 20 endpoints covering core functionality including create menu, all menus, menu by id.

Call POST /menu to create menu

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

Why though Jentic?

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

Credential isolation

Config API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create menu') and Jentic returns the matching Config API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Config API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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

What authentication does the Config API use?

The Config API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.