canonical: https://jentic.com/apis/swaggerhub.frank-kilcommins/bookstore-api

# Frank Kilcommins Bookstore API

The **Books API** - allows searching of books from the book catalog as well as retrieving the specific details on a selected book. Once you find the book you are looking for, you can make an order. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get a list of books based on the provided criteria, place book order. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get a list of books based on the provided criteria
- Place book order
- Integrate Bookstore API into automated workflows
- Query and filter Bookstore API records by parameters
- Monitor Bookstore API operational status and events

## Use cases

### E-Commerce Operations

Use the Bookstore API to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including get a list of books based on the provided criteria, place book order.

Example prompt: Call GET /books to get a list of books based on the provided criteria

### Data Retrieval and Monitoring

Query Bookstore API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Bookstore API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'get a list of books based on the provided criteria', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /books | Get a list of books based on the provided criteria |
| POST | /orders | Place book order |

## Key resources

- **Bookstore** — APIs for our fictional bookstore

## Why Jentic

- **Setup:** Wiring the Bookstore API by hand means sending its api_key header on every request and coding the book search and order flows against the host yourself. Through Jentic you install once, import Bookstore API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Bookstore API takes its parameters in the query and body rather than a resource id in the path, so scope the agent to the operations it needs, such as listing books. You choose the operations it may call, so placing an order is not included unless you add it.
- **Credential handling:** Your Bookstore API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'find books matching these criteria' or 'place a book order', and Jentic returns the matching Bookstore API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Bookstore API use?

The Bookstore API uses an API key passed in the `api_key` header. 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 get a list of books based on the provided criteria with the Bookstore API?

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

### What are the rate limits for the Bookstore 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 get a list of books based on the provided criteria through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get a list of books based on the provided criteria'. Jentic returns the matching Bookstore API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bookstore API have?

The Bookstore API exposes 2 endpoints covering bookstore operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Bookstore API operations and credentials the agent can use. The Bookstore API has just two operations, GET /books to list books and POST /orders to place an order, so you can grant the agent read-only book search and withhold order placement until you choose to add it. Since the parameters live in the query and body rather than a path id, you scope access at the operation level and the agent can only call what you have allowed.