For Agents
Push JS, CSS, or HTML snippets into the frontend of an itembase-connected merchant storefront — create, retrieve, update, or remove the snippets via per-connection endpoints.
Install Jentic One Beta
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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 instanceJentic 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.
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
GET STARTED
Use for: Create a new tracking pixel snippet for a merchant connection, Get the current snippet content for a specific connection, I want to update the conversion script across all connected merchants, Delete an obsolete promotional snippet from a merchant frontend
Not supported: Does not handle product catalogues, orders, or merchant authentication — use for delivering frontend JS, CSS, and HTML snippets only.
Jentic publishes the only available OpenAPI specification for itembase Frontend Manipulation API, keeping it validated and agent-ready. The API delivers JS, CSS, and HTML snippets to the storefront of merchants connected through itembase. Each snippet is scoped by a connection identifier and is created, listed, updated, or deleted via the four /data/v2/connections/{connection_id}/snippet endpoints. The pattern is used for embedding partner widgets, conversion tracking pixels, or merchant-specific UI overrides without redeploying the storefront itself.
Remove a snippet to retire a partner integration cleanly
Manage many merchant connections from a single integration codebase using connection_id as the key
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
4 endpoints — jentic publishes the only available openapi specification for itembase frontend manipulation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/data/v2/connections/{connection_id}/snippet
Create a snippet for a merchant connection
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Retrieve a snippet by id
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Update an existing snippet
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Remove a snippet
/data/v2/connections/{connection_id}/snippet
Create a snippet for a merchant connection
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Retrieve a snippet by id
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Update an existing snippet
/data/v2/connections/{connection_id}/snippet/{snippet_id}
Remove a snippet
Three things that make agents converge on Jentic-routed access.
Credential isolation
Any itembase partner credential is encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw partner key never enters the agent context, which matters because snippets execute inside merchant storefronts.
Intent-based discovery
Agents search by intent (e.g. 'push frontend snippet to merchant') and Jentic returns the matching itembase operation with its connection and snippet identifier parameters.
Time to first call
Direct itembase integration: half a day to wire the partner connection model and snippet lifecycle. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using itembase Frontend Manipulation API through Jentic.
Why is there no official OpenAPI spec for itembase Frontend Manipulation API?
itembase publishes documentation through SwaggerHub but the spec is alpha-tagged and is not consistently mirrored on the vendor site. Jentic generates and maintains this spec so that AI agents and developers can call the Frontend Manipulation API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the itembase Frontend API use?
The OpenAPI document does not declare a security scheme — practical access is gated by the connection_id the partner is allowed to address, with auth handled at the partner-account boundary. Through Jentic any partner-level credential is held in the vault and injected at request time.
Can I update a snippet without recreating it?
Yes. Call PUT /data/v2/connections/{connection_id}/snippet/{snippet_id} with the new payload to replace the snippet content in place. The snippet identifier remains stable for downstream tracking.
What are the rate limits for the itembase Frontend API?
Rate limits are not declared in the spec. itembase applies fair-use throttling tied to the partner account, which is generous for typical rollout volumes. Confirm the per-account limit before scripting a fan-out across thousands of connections.
How do I retire a snippet through Jentic?
Search Jentic with the query 'delete itembase frontend snippet', load the DELETE /data/v2/connections/{connection_id}/snippet/{snippet_id} operation, and execute it with the connection and snippet identifiers. The merchant storefront stops loading the snippet on the next page render.
Is the API only for JavaScript snippets?
It supports JS, CSS, and HTML payloads — the snippet body is treated as opaque content delivered to the frontend. Use whichever asset type the integration requires, but be aware that CSS and HTML override the merchant's native theme and need careful change control.