Install Jentic One Beta

Connect the RZQ API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RZQ API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frzq.com%2Frzq" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frzq.com%2Frzq" | 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 RZQ API.

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

GET STARTED

Start building with RZQ API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'create a queue', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — api for resource and queue management.

METHOD

PATH

DESCRIPTION

POST

/queues

Create a queue

GET

/queues

List queues

POST

/messages

Add message to queue

POST

/queues

Create a queue

GET

/queues

List queues

POST

/messages

Add message to queue

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using RZQ API through Jentic.

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.

RZQ API

Name: RZQ API
Brand: RZQ API
Availability: InStock

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

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

Use for: I need to a queue, I want to queues, Search for add message to queue, List all records from RZQ API

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

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

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RZQ API to your agent

Capabilities

Use Cases

Start building with RZQ API

Key Endpoints

Why Jentic?

Related APIs

FAQs

RZQ API

Jentic AI Readiness Score

RZQ API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness