Install Jentic One Beta

Connect the Shoprocket API to your agent

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

create_account_with_paramaters

create_account_no_paramaters

create_delete_with_paramaters

create_delete_no_paramaters

create_list_with_paramaters

GET STARTED

Start building with Shoprocket API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Shoprocket API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Shoprocket API to perform identity auth operations programmatically. The API provides 53 endpoints covering core functionality including create_account_with_paramaters, create_account_no_paramaters, create_delete_with_paramaters.

Call GET /account/create/{email}{password}{companyname}{partnerkey} to create_account_with_paramaters

Automated Account Management

Automate account operations by combining multiple Shoprocket API endpoints. Agents can create_account_no_paramaters and then create_delete_with_paramaters in a single workflow.

Call POST /account/create to create_account_no_paramaters, then verify the result

AI Agent Integration via Jentic

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

Key Endpoints

53 endpoints — the shoprocket api.

METHOD

PATH

DESCRIPTION

GET

/account/create/{email}{password}{companyname}{partnerkey}

create_account_with_paramaters

POST

/account/create

create_account_no_paramaters

GET

/account/delete/{companyid}{authkey}{partnerkey}

create_delete_with_paramaters

POST

/account/delete

create_delete_no_paramaters

GET

/account/list/{companyid}{authkey}{partnerkey}

create_list_with_paramaters

POST

/account/list

create_list_no_paramaters

GET

/account/livestate/{companyid}{authkey}{partnerkey}

create_livestate_with_paramaters

POST

/account/logintoken

create_logintoken_with_paramaters

GET

/account/create/{email}{password}{companyname}{partnerkey}

create_account_with_paramaters

POST

/account/create

create_account_no_paramaters

GET

/account/delete/{companyid}{authkey}{partnerkey}

create_delete_with_paramaters

POST

/account/delete

create_delete_no_paramaters

GET

/account/list/{companyid}{authkey}{partnerkey}

create_list_with_paramaters

POST

/account/list

create_list_no_paramaters

GET

/account/livestate/{companyid}{authkey}{partnerkey}

create_livestate_with_paramaters

POST

/account/logintoken

Why Jentic?

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

Setup

Wiring the Shoprocket API by hand means threading the company id, auth key, and partner key through each account path against dev.shoprocket.co and parsing the responses yourself. Through Jentic you install once, import the Shoprocket API from the API Directory, and your agent calls it with the account keys configured in one place.

Permission scoping

Shoprocket carries its keys and ids in the request rather than as owned path resources, so you limit the agent to the operations it needs, such as creating an account or listing accounts, and destructive ones like account deletion stay out unless you add them.

Credential isolation

Any Shoprocket keys your agent needs are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an account with parameters' or 'get account live state', and Jentic returns the matching Shoprocket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Shoprocket API through Jentic.

What authentication does the Shoprocket API use?

The Shoprocket 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_account_with_paramaters with the Shoprocket API?

Yes. Use the GET /account/create/{email}{password}{companyname}{partnerkey} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Shoprocket 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_account_with_paramaters through Jentic?

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

How many endpoints does the Shoprocket API have?

The Shoprocket API exposes 53 endpoints covering account, app, cart operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Shoprocket operations and credentials the agent can use. You can allow only the calls the agent needs, such as creating an account or listing accounts, while keeping destructive operations like account deletion out of reach unless you explicitly add them. Since Shoprocket carries its company id, auth key, and partner key in each request rather than as owned resources, this operation-level allowlist is how you control the agent's access.

Shoprocket API

Name: Shoprocket API
Brand: Shoprocket API
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

Community OpenAPI document · agent-readyIdentity AuthAuthenticationnone53 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create_account_with_paramaters, create_account_no_paramaters. Covers 53 operations.

Use for: I need to create_account_with_paramaters, I want to create_account_no_paramaters, Search for create_delete_with_paramaters, Find all create_delete_no_paramaters

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

The Shoprocket API. This is the private API and is under rapid development. Endpoints may change be added to and removed. Also some endpoits are symbolic in nature such as session and voucher which at this moment in time reside in the cart end point. By the they are promoted to the public API they will most likely be under the session voucher methods and not the cart. This is one example of the th. The API exposes 53 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

39%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

63%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

92%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Shoprocket API to your agent

Capabilities

Start building with Shoprocket API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Shoprocket API

Jentic AI Readiness Score

Shoprocket API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness