Install Jentic One Beta

Connect the itembase Frontend Manipulation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the itembase Frontend Manipulation 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%2Fitembase.io%2Fitembase" | 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%2Fitembase.io%2Fitembase" | 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 itembase Frontend Manipulation API.

Push a new JavaScript or HTML snippet into a connected merchant storefront

Update an existing snippet to roll out a fix without re-deploying the storefront

Retrieve the current snippet content stored against a connection for audit

Remove a snippet to retire a partner integration cleanly

GET STARTED

Start building with itembase Frontend Manipulation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use itembase Frontend Manipulation API for, with concrete tasks.

★ Partner pixel deployment across connected merchants

Roll out an analytics or remarketing pixel across many itembase-connected merchant storefronts by calling POST /data/v2/connections/{connection_id}/snippet for each connection. The API delivers the snippet to the merchant frontend without needing the merchant to touch their own template files. Replaces the bespoke per-merchant deployment process that partners would otherwise need.

For each connection in the supplied list, POST /data/v2/connections/{connection_id}/snippet with the supplied JavaScript pixel body

Versioned A/B testing of frontend scripts

Run A/B tests of a frontend enhancement script by writing variant snippets to subsets of connections through PUT /data/v2/connections/{connection_id}/snippet/{snippet_id}. The agent rotates which variant is live by updating the snippet body, and rolls back instantly with another PUT if metrics degrade. Avoids the lag of waiting for a merchant to redeploy their store.

Update snippet abc123 on connection xyz456 to the variant B JavaScript body and record the rollout time

Auditable snippet inventory for compliance

Maintain an auditable inventory of every script running on connected merchants by calling GET /data/v2/connections/{connection_id}/snippet/{snippet_id} on a schedule. The agent stores hashes of each snippet body and flags drift between expected and actual content. Useful for partners that need to demonstrate compliance with merchant security baselines.

For each connection in the partner workspace, fetch all snippets and record their content hashes

AI agent rolling out merchant-specific banners

An AI agent supporting a partner success team can deploy a custom banner snippet to a single merchant in seconds. Through Jentic the agent searches for 'create itembase frontend snippet' and the matching operation is loaded - the agent only needs the connection id and snippet body. Removes a manual step from the partner support workflow.

Push the supplied banner HTML to connection xyz456 as a new snippet and return the snippet id

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for itembase frontend manipulation api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/data/v2/connections/{connection_id}/snippet

Create a snippet for a merchant connection

GET