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

# RZQ API

API for resource and queue management. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a queue, list queues. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a queue
- List queues
- Add message to queue
- Query and filter RZQ API records by parameters
- Monitor RZQ API operational status and events

## Use cases

### Developer Tools Operations

Use the RZQ API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including create a queue, list queues, add message to queue.

Example prompt: Call POST /queues to create a queue

### Automated messages Management

Automate messages operations by combining multiple RZQ API endpoints. Agents can list queues and then add message to queue in a single workflow.

Example prompt: Call GET /queues to list queues, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RZQ 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 'create a queue', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/queues` | Create a queue |
| GET | `/queues` | List queues |
| POST | `/messages` | Add message to queue |

## Key resources

- **messages** — Operations related to messages
- **queues** — Operations related to queues

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rzq.com/rzq/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the RZQ API by hand means managing its API key, attaching it to each call against api.rzq.com, and handling your own retries. Through Jentic you install once, import the RZQ API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The RZQ API takes queue and message details in the request body rather than the URL path, so scope the agent to the operations it needs, such as listing queues, and leave out creating queues or posting messages unless the agent needs them.
- **Credential handling:** Your RZQ 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 'create a queue' or 'send a message to a queue', and Jentic returns the matching RZQ API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the RZQ API use?

The RZQ API uses an API key passed 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 create a queue with the RZQ API?

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

### What are the rate limits for the RZQ 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 create a queue through Jentic?

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

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

The RZQ API exposes 3 endpoints covering messages, queues operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which RZQ API operations and credentials the agent may use. Since queue and message details travel in the request body rather than the URL path, you can scope the agent to just the operations it needs, such as GET /queues to list queues, and leave out POST /queues for creating queues or POST /messages for posting messages unless the agent requires them. The stored API key is injected only for the operations you permit.