Install Jentic One Beta

Connect the 1WorldSync Content1 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 1WorldSync Content1 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%2Fmarketplace.api.1worldsync.com%2F1worldsync" | 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%2Fmarketplace.api.1worldsync.com%2F1worldsync" | 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 1WorldSync Content1 API.

Search the 1WorldSync product catalogue with /products including filters and pagination parameters

Retrieve a single product's full content payload via /products/{itemReferenceId}

Pull brand-supplied descriptions, attributes, marketing copy, and digital asset references for a product

GET STARTED

Start building with 1WorldSync Content1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use 1WorldSync Content1 API for, with concrete tasks.

★ Retailer Catalogue Backfill

Retailers and marketplaces call /products on a schedule to pull batches of newly onboarded SKUs and /products/{itemReferenceId} for the full content payload of each one. The brand-supplied descriptions, attributes, and digital assets land directly in the retailer's PIM and replace lower-quality data scraped from supplier feeds. A first integration takes a few days including pagination and PIM mapping.

Page through /products filtered to a target brand, then call /products/{itemReferenceId} for each result and write the response to the retailer's PIM staging table.

Product Detail Page Enrichment

E-commerce platforms call /products/{itemReferenceId} to enrich a product detail page with authoritative manufacturer copy, structured attributes, and digital assets. Because the content originates with the brand owner it improves discoverability and conversion versus scraped or supplier-supplied descriptions. Typical wiring is half a day behind a CMS template.

Call /products/{itemReferenceId} with the SKU's reference ID and return the localised description, marketing copy, and the first three image asset URLs.

Marketplace Onboarding Validation

Marketplace onboarding pipelines call /products to confirm that a seller-supplied SKU exists in the 1WorldSync network and /products/{itemReferenceId} to compare the seller's submitted attributes against the brand owner's authoritative record. Discrepancies are flagged for the seller to correct before listing goes live, which reduces returns and listing-quality complaints.

Search /products for a candidate GTIN, fetch /products/{itemReferenceId} for the matching record, and return any attribute where the seller's submission differs from the master.

Digital Asset Sync

Digital asset management (DAM) tools call /products/{itemReferenceId} to pull the brand owner's official image, video, and document links and mirror them into the retailer's CDN. This keeps creative assets aligned with the brand's latest packaging and marketing without manual asset uploads.

Call /products/{itemReferenceId} for a list of SKUs and return only the digital asset URLs grouped by asset type (image, video, document).

AI Agent Catalogue Operations

An AI agent embedded in a retailer's catalogue operations team calls 1WorldSync Content1 through Jentic to look up master records, refresh stale content, and backfill new SKUs without bespoke client code. Jentic exposes both endpoints as typed tools with discoverable input schemas so the agent picks /products vs /products/{itemReferenceId} based on whether it is searching or fetching.

Search Jentic for 'fetch a 1WorldSync product record', load the schema for /products/{itemReferenceId}, and execute the call for the SKU's reference ID supplied by the user.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for 1worldsync content1 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

Search the 1WorldSync product catalogue

GET

/products/{itemReferenceId}

Fetch a single product record

GET

/products

Search the 1WorldSync product catalogue

GET

/products/{itemReferenceId}

Fetch a single product record

Why Jentic?

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

Setup

Wiring 1WorldSync Content1 by hand means arranging the credential pattern from your 1WorldSync contract, learning the two /products endpoints, and parsing the product content yourself. Through Jentic you install once, import the 1WorldSync Content1 API from the API Directory, store the contract credential once, and your agent calls it.

Permission scoping

The two Content1 endpoints are read-only product lookups, so scoping is by operation: you limit the agent to the operations it needs, such as searching products or fetching one by its item reference id, and leave out the other if you do not want it called. Every operation you allow is one you have chosen, so the agent stays inside that set.

Credential isolation

Your 1WorldSync credential is stored once, encrypted, by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'fetch a 1WorldSync product record' or 'search 1WorldSync products', and Jentic returns the matching Content1 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using 1WorldSync Content1 API through Jentic.

Why is there no official OpenAPI spec for 1WorldSync Content1 API?

1WorldSync does not publish an OpenAPI specification on its public marketing site. Jentic generates and maintains this spec so that AI agents and developers can call 1WorldSync Content1 API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the 1WorldSync Content1 API use?

The published spec does not declare a security scheme. In practice 1WorldSync issues per-customer credentials at contract signing and access is controlled at the network level; refer to your 1WorldSync onboarding pack for the exact credential pattern your account uses.

Can I retrieve a single product's full content record?

Yes. GET /products/{itemReferenceId} returns the full content payload for one product including identifiers, attributes, localised descriptions, and digital asset references. Use GET /products to discover the item reference IDs first.

What are the rate limits for the 1WorldSync Content1 API?

Rate limits are negotiated per customer contract rather than published in the spec. Production callers should batch search calls and cache /products/{itemReferenceId} responses for the typical content refresh interval agreed with 1WorldSync.

How do I backfill a retailer PIM through Jentic?

Run `pip install jentic`, search for 'list 1WorldSync products' and 'fetch a 1WorldSync product record', and chain the two operations: page through GET /products and call GET /products/{itemReferenceId} for each hit. Jentic loads the input schema for each endpoint.

Does 1WorldSync return localised product descriptions?

Yes. The /products/{itemReferenceId} response carries localised marketing copy and descriptions when the brand owner has supplied them, which is how retailers populate region-specific storefronts from a single source of truth.

Can I limit what my agent is allowed to do with the 1WorldSync Content1 API?

Yes. Because you run Jentic One yourself, your own rules decide which of the two read-only Content1 operations your agent may call: searching the product catalogue with GET /products or fetching one record with GET /products/{itemReferenceId}. You can allow only the operation the agent needs and leave the other out, so the agent stays inside the set you have chosen. Your 1WorldSync credential is applied at execution time and never enters the agent's prompt or logs.

Marketplace Api 1worldsync 1WorldSync Content1 API

Name: 1WorldSync Content1 API
Brand: 1WorldSync Content1 API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceStorefrontnone2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search and retrieve trusted brand-supplied product content from the 1WorldSync network through two endpoints - list products and fetch a single product by reference ID.

Use for: Search 1WorldSync for products matching a brand or category, Retrieve the full product content record for a given item reference ID, Pull localised product descriptions for a SKU before publishing to a regional storefront, Get the official digital asset list for a SKU including hero images and instruction sheets

Not supported: Does not handle order processing, inventory levels, pricing, or storefront management - use for retrieving brand-supplied product content from the 1WorldSync network only.

Jentic publishes the only available OpenAPI specification for 1WorldSync Content1 API, keeping it validated and agent-ready. 1WorldSync Content1 provides retailer-grade product content sourced directly from brand owners through 1WorldSync's product information network. The two endpoints expose a product search at /products and a single-product detail lookup at /products/{itemReferenceId}. Typical responses include identifiers (GTIN, UPC), localised descriptions, attributes, marketing copy, and digital assets. The API is positioned for retailers, marketplaces, and product information management (PIM) systems that need authoritative manufacturer-supplied product content.

Jentic One on Github View OpenAPI Document