Usac93 AMS
Browse all Swaggerhub Usac93 APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey, oauth220 EndpointsREST
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.
This is a sample Petstore server. You can find out more about Swagger at [http://swagger.io](http://swagger.io) or on [irc.freenode.net, #swagger](http://swagger.io/irc/). The API exposes 20 endpoints secured with apiKey, oauth2 authentication.
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.
1
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 | sh2
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 instanceJentic 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
Deletes a pet
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
/pet/{petId}
Find pet by ID
DELETE
/pet/{petId}
Deletes a pet
POST
/pet/{petId}/uploadImage
uploads an image
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AMS apiKey, oauth2 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., 'add a new pet to the store') and Jentic returns the matching AMS operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct AMS 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.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED