Antique Shop API

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone30 EndpointsREST

For Agents

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

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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 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 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

GET STARTED

Start building with Antique Shop API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Antique Shop API API for, with concrete tasks.

★ Developer Tools Operations

Use the Antique Shop API to perform developer tools operations programmatically. The API provides 30 endpoints covering core functionality including assign a new role to a user, update the authenticated user's profile, update the authenticated user's password.

Call PUT /users/upd-role to assign a new role to a user

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Antique Shop API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'assign a new role to a user') and Jentic returns the matching Antique Shop API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Antique Shop API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Antique Shop API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.