Install Jentic One Beta

Connect the Antique Shop API to your agent

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

Assign a new role to a user

Update the authenticated user's profile

Reset the authenticated user's password

Retrieve a product by ID

Delete a product

GET STARTED

Start building with Antique Shop API

Explore with Jentic One

View OpenAPI Document

Automated Category management Management

Automate category management operations by combining multiple Antique Shop API endpoints. Agents can update the authenticated user's profile and then update the authenticated user's password in a single workflow.

Call PUT /users/me/upd-profile to update the authenticated user's profile, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Antique Shop 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 'assign a new role to a user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

30 endpoints — api documentation for the antique shop application.

METHOD

PATH

DESCRIPTION

PUT

/users/upd-role

Assign a new role to a user

PUT

/users/me/upd-profile

Update the authenticated user's profile

PUT

/users/me/upd-pass

Update the authenticated user's password

PUT

/users/me/reset-pass

Reset the authenticated user's password

GET

/products/{id}

Retrieve a product by ID

PUT

/products/{id}

Update a product

DELETE

/products/{id}

Delete a product

GET

/categories/{id}

Get a category by ID

PUT

/users/upd-role

Assign a new role to a user

PUT

/users/me/upd-profile

Update the authenticated user's profile

PUT

/users/me/upd-pass

Update the authenticated user's password

PUT

/users/me/reset-pass

Reset the authenticated user's password

GET

/products/{id}

Retrieve a product by ID

PUT

/products/{id}

Update a product

DELETE

/products/{id}

Delete a product

GET

/categories/{id}

Get a category by ID

Why Jentic?

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

Setup

Wiring the Antique Shop API by hand means reading its OpenAPI definition, pointing at its hosted server, and hand-coding each product, category, and user operation with its retries yourself. Through Jentic you install once, import the Antique Shop API from the API Directory, store any credential it needs once, and your agent calls it.

Permission scoping

The Antique Shop API puts the product id in the URL path (/products/{id}), so a rule can pin your agent to one product: it can read that product and nothing else. You choose the operations it may call, so destructive ones like updating or deleting a product, or changing a user's role, are not included unless you add them.

Credential isolation

Any credential this API requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search products by category' or 'fetch a product by id', and Jentic returns the matching Antique Shop API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Antique Shop API through Jentic.

What authentication does the Antique Shop API use?

The Antique Shop 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 assign a new role to a user with the Antique Shop API?

Yes. Use the PUT /users/upd-role endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Antique Shop 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 assign a new role to a user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'assign a new role to a user'. Jentic returns the matching Antique Shop API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Antique Shop API have?

The Antique Shop API exposes 30 endpoints covering category management, authentication, user management operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Antique Shop API operations and credentials the agent may use, so you can grant read-only access like GET /products/{id} while withholding destructive ones such as PUT /products/{id}, DELETE /products/{id}, or PUT /users/upd-role. Since the product id sits in the URL path, a rule can pin the agent to a single product, letting it read that product and nothing else. Any operation you do not explicitly add stays off limits to the agent.

Dorofieieva Antique Shop API

Name: Antique Shop API
Brand: Antique Shop API
Availability: InStock

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone30 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically assign a new role to a user, update the authenticated user's profile. Covers 30 operations.

Use for: I need to assign a new role to a user, I want to the authenticated user's profile, Search for the authenticated user's password, Find all reset the authenticated user's password

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

API documentation for the Antique Shop application. The API exposes 30 endpoints.

Jentic One on Github View OpenAPI Document

Connect the Antique Shop API to your agent

Capabilities

Start building with Antique Shop API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dorofieieva Antique Shop API