canonical: https://jentic.com/apis/rejax.io/rejax

# Rejax API

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

## For AI agents

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

## Scope

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

## Capabilities

- 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

### Developer Tools Operations

Use the Rejax API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including list requests, get request details, proxy http request.

Example prompt: Call GET /requests to list requests

### 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list requests', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/requests` | List requests |
| GET | `/requests/{id}` | Get request details |
| POST | `/proxy` | Proxy HTTP request |
| GET | `/status` | Get API status |

## Key resources

- **proxy** — Operations related to proxy
- **requests** — Operations related to requests
- **status** — Operations related to status

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/rejax.io/rejax/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

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

## FAQ

### 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.