canonical: https://jentic.com/apis/queryvary.com/queryvary

# Query Vary API

Query Vary API for sending prompts to AI templates and retrieving AI-generated responses with token usage metrics. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically send chat message. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Send Chat Message
- Access Query Vary API identity auth resources via REST API
- Query Query Vary API endpoints with structured JSON responses
- Authenticate requests with bearer credentials managed by Jentic
- Access Query Vary API resources programmatically via REST

## Use cases

### Identity and Authentication Operations

Use the Query Vary API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including send chat message.

Example prompt: Call POST `/qv1/chat` to send chat message

### Data Retrieval and Monitoring

Query Query Vary API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.

Example prompt: Query the Query Vary API API to retrieve current data and verify the response structure

### AI Agent Integration via Jentic

AI agents discover and call Query Vary 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 bearer tokens manually.

Example prompt: Search Jentic for 'send chat message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/qv1/chat` | Send Chat Message |

## Key resources

- **Chat** — Operations related to Chat

## Why Jentic

- **Setup:** Wiring the Query Vary API by hand means setting its bearer Authorization header on each call to api.queryvary.com and handling the chat responses yourself. Through Jentic you install once, import the Query Vary API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Query Vary API exposes a single chat operation (`/qv1/chat`) rather than a resource id in the path, so scope by operations: limit the agent to the operations it needs, such as sending a chat message. You choose which operations are in that set, and the agent can call only those.
- **Credential handling:** Your Query Vary bearer token 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 'send a chat message', and Jentic returns the matching Query Vary operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Query Vary API use?

The Query Vary API uses a Bearer token in the Authorization 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 send chat message with the Query Vary API?

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

### What are the rate limits for the Query Vary 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 send chat message through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send chat message'. Jentic returns the matching Query Vary API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Query Vary API have?

The Query Vary API exposes 1 endpoints covering chat operations.

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

Yes. The Query Vary API exposes a single chat operation, POST `/qv1/chat`, so you scope access by operation rather than by resource. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, so you can allow only sending a chat message and nothing else. The agent can call only the operations you include in that set, and your bearer token is injected at execution time so it never enters the agent's context.