Install Jentic One Beta

Connect the Rejax API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rejax 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%2Frejax.io%2Frejax" | 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%2Frejax.io%2Frejax" | 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 Rejax API.

List requests

Get request details

Proxy HTTP request

Query and filter Rejax API records by parameters

Monitor Rejax API operational status and events

Use Cases

GET STARTED

Start building with Rejax API

Explore with Jentic One

View OpenAPI Document

Automated proxy Management

Automate proxy operations by combining multiple Rejax API endpoints. Agents can get request details and then proxy http request in a single workflow.

Call GET /requests/{id} to get request details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rejax 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 'list requests', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — rejax api provides http request services and testing capabilities.

METHOD

PATH

DESCRIPTION

GET

/requests

List requests

GET

/requests/{id}

Get request details

POST

/proxy

Proxy HTTP request

GET

/status

Get API status

GET

/requests

List requests

GET

/requests/{id}

Get request details

POST

/proxy

Proxy HTTP request

GET

/status

Get API status

Why Jentic?

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

Setup

Wiring Rejax by hand means setting up its X-API-Key header auth against api.rejax.io and proxying requests through its endpoints yourself. Through Jentic you install once, import Rejax from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rejax puts the request id in the URL path (/requests/{id}), so a rule can pin your agent to reading one request and checking status. You choose the operations it may call, so the proxy POST is not included unless you add it.

Credential isolation

Your Rejax 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 'list requests' or 'check proxy status', and Jentic returns the matching Rejax operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Rejax API through Jentic.

What authentication does the Rejax API use?

The Rejax API uses an API key passed in the `X-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 list requests with the Rejax API?

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

What are the rate limits for the Rejax 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 list requests through Jentic?

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

How many endpoints does the Rejax API have?

The Rejax API exposes 4 endpoints covering proxy, requests, status operations.

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

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which Rejax operations and credentials the agent may use. Since Rejax puts the request id in the URL path (/requests/{id}), you can pin the agent to reading a single request with GET /requests/{id} and checking GET /status, while leaving out the POST /proxy operation unless you explicitly allow it. Only the operations you choose are exposed to the agent.

Rejax API

Name: Rejax API
Brand: Rejax API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting QaapiKey4 EndpointsREST

For Agents

Programmatically list requests, get request details. Covers 4 operations with apiKey authentication.

Use for: I need to requests, I want to request details, Search for proxy http request, Find all API status

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

Rejax API provides HTTP request services and testing capabilities. The API exposes 4 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Rejax API to your agent

Capabilities

Use Cases

Start building with Rejax API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rejax API