canonical: https://jentic.com/apis/api.revreply.com/revreply

# RevReply API

Jentic publishes the only available OpenAPI specification for the RevReply API, keeping it validated and agent-ready. The RevReply API reports the service's operational status through a single status endpoint. It returns whether the API is available, so an agent can confirm health before it depends on the service.

## For AI agents

Check the operational status of the RevReply service through a single status endpoint. Confirm the API is available before starting a workflow that depends on it.

## Scope

Does not handle review replies, incident management, or alerting. Use for reading the service's operational status only.

## Capabilities

- Check the current operational status of the RevReply service
- Confirm the API is available before starting a workflow
- Poll service health as part of a monitoring routine

## Use cases

### Service Health Check Agent

An AI agent confirms RevReply is reachable before it runs a workflow that depends on the service, calling the status endpoint and branching on the result. Through Jentic the agent discovers the status operation by intent and calls it directly, so a failed dependency is caught before work begins.

Example prompt: Call the status endpoint and stop the workflow if the service is unavailable

### Pre-Flight Availability Check

Before a scheduled job starts, an agent checks the status endpoint and defers the run when the service is down. This avoids partial work against an unavailable API and keeps retries clean.

Example prompt: Verify the service is available and defer the job if it is not

### Uptime Monitoring

A monitoring routine polls the status endpoint on a schedule and records the result, alerting when the service stops responding. The agent turns a simple status read into an availability signal for a dashboard.

Example prompt: Poll the status endpoint and record whether the service is available

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/status` | Get the service operational status |

## Key resources

- **Status** — Read the current operational status of the service

## Why Jentic

- **Setup:** Wiring the RevReply API by hand means handling its bearer-token auth and the status request yourself. Through Jentic you install once, import RevReply from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** RevReply exposes one status operation that only reads availability, so scoping is about whether the agent may call it, not which record it touches. You allow that operation explicitly, and every call it makes is logged.
- **Credential handling:** Your RevReply 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 'check service status', and Jentic returns the RevReply status operation with its input schema so the agent reads availability without browsing the reference docs.

## Related APIs

- **UptimeRobot** — Uptime monitoring service compared with RevReply's status endpoint
- **Pingdom** — Uptime and performance monitoring versus RevReply's status check
- **Statuspage** — Public status pages that pair with RevReply's status signal

## FAQ

### What authentication does the RevReply API use?

The RevReply API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### Can I check the service status with the RevReply API?

Yes. Call GET /status to read whether the API is available. An agent can branch on the result to decide whether to proceed with work that depends on the service.

### What are the rate limits for the RevReply API?

The OpenAPI spec does not specify rate limits. Check the RevReply documentation at https://api.revreply.com before polling the status endpoint at high frequency.

### Why is there no official OpenAPI spec for the RevReply API?

RevReply does not publish its own OpenAPI description. Jentic maintains this specification from the documented status endpoint and keeps it validated so agents can call the API reliably.

### Is there a RevReply MCP server?

You don't need an MCP server to give your agent the RevReply API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the status operation.

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

Yes. RevReply exposes one status operation that only reads availability, so a rule controls whether the agent may call it, and every call it makes is logged.

### How do I check the service status with the RevReply API through Jentic?

Search Jentic for 'check service status', and it returns the GET /status operation with its input schema so your agent reads availability directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.