Usac93 AMS

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey, oauth220 Endpoints

Install Jentic One Beta

Connect the AMS to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AMS, 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 | sh

Step 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 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 AMS API.

Add a new pet to the store

Update an existing pet

Finds Pets by status

Find pet by ID

GET STARTED

Start building with AMS API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically add a new pet to the store, update an existing pet. Covers 20 operations with apiKey, oauth2 authentication.

Use for: I need to add a new pet to the store, I want to an existing pet, Search for finds pets by status, Find all finds pets by tags

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

Use Cases

Patterns agents use AMS API for, with concrete tasks.

★ Cloud Infrastructure Operations

Use the AMS to perform cloud infrastructure operations programmatically. The API provides 20 endpoints covering core functionality including add a new pet to the store, update an existing pet, finds pets by status.

Call POST /pet to add a new pet to the store

Automated pet Management

Automate pet operations by combining multiple AMS endpoints. Agents can update an existing pet and then finds pets by status in a single workflow.

Call PUT /pet to update an existing pet, then verify the result

AI Agent Integration via Jentic

AI agents discover and call AMS 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 apiKey, oauth2 tokens manually.

Search Jentic for 'add a new pet to the store', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — this is a sample petstore server.

METHOD

PATH

DESCRIPTION

POST

/pet

Add a new pet to the store

PUT

/pet

Update an existing pet

GET

/pet/findByStatus

Finds Pets by status

GET

/pet/findByTags

Finds Pets by tags

POST

/pet/{petId}

Updates a pet in the store with form data

GET

/pet/{petId}

Find pet by ID

DELETE

/pet/{petId}

Deletes a pet

POST

/pet/{petId}/uploadImage

uploads an image

POST

/pet

Add a new pet to the store

PUT

/pet

Update an existing pet

GET

/pet/findByStatus

Finds Pets by status

GET

/pet/findByTags

Finds Pets by tags

POST

/pet/{petId}

Updates a pet in the store with form data

GET

Why Jentic?

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

Credential isolation

Your AMS API key and OAuth2 credentials 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 'add a new pet to the store' or 'find pets by status', and Jentic returns the matching AMS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using AMS API through Jentic.

What authentication does the AMS use?

The AMS uses apiKey, oauth2 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 add a new pet to the store with the AMS?

Yes. Use the POST /pet endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the AMS?

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 add a new pet to the store through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a new pet to the store'. Jentic returns the matching AMS operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the AMS have?

The AMS exposes 20 endpoints covering pet, store, user operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which AMS operations and credentials the agent can use. Since AMS puts the pet id in the URL path (/pet/{petId}), a rule can pin the agent to a single record so it only reads and updates that pet and nothing else. You also choose which operations are in scope, so destructive calls like DELETE /pet/{petId} stay off limits unless you explicitly allow them.

Usac93 AMS

Connect the AMS to your agent

Capabilities

Start building with AMS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs