canonical: https://jentic.com/apis/refugerestrooms.org/refugerestrooms

# Refugerestrooms API title

refugerestrooms.org/main version 0.0.1. The API exposes 4 endpoints.

## For AI agents

Programmatically getv1restrooms, getv1restroomsbydate. Covers 4 operations.

## Scope

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

## Capabilities

- getV1Restrooms
- Manage developer tools data programmatically
- Integrate API title into automated workflows
- Query and filter API title records by parameters
- Monitor API title operational status and events

## Use cases

### Developer Tools Operations

Use the API title to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including getv1restrooms, getv1restroomsbydate, getv1restroomsbylocation.

Example prompt: Call GET `/v1/restrooms` to getv1restrooms

### Automated restrooms Management

Automate restrooms operations by combining multiple API title endpoints. Agents can getv1restroomsbydate and then getv1restroomsbylocation in a single workflow.

Example prompt: Call GET `/v1/restrooms/by_date` to getv1restroomsbydate, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API title 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/restrooms` | getV1Restrooms |
| GET | `/v1/restrooms/by_date` | getV1RestroomsByDate |
| GET | `/v1/restrooms/by_location` | getV1RestroomsByLocation |
| GET | `/v1/restrooms/search` | getV1RestroomsSearch |

## Key resources

- **restrooms** — Operations about restrooms

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 55 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 59 / 100
- **View full report:** https://jentic.com/apis/refugerestrooms.org/refugerestrooms/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:** The Refuge Restrooms API needs no authentication, so wiring it by hand still means building your own request and retry handling against its read-only restroom endpoints. Through Jentic you install once, import the API from the API Directory, and your agent calls it with no key to manage.
- **Permission scoping:** The Refuge Restrooms API exposes read-only listing and search endpoints with parameters in the query, so scoping is by operation: limit the agent to the operations it needs, such as searching restrooms or listing them by location, rather than to a single record. Every operation is read-only and available only if you include it.
- **Credential handling:** The Refuge Restrooms API needs no credential, so there is nothing to store: your Jentic One instance simply executes the read-only calls. No secret ever enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find restrooms near a location' or 'search restrooms by date', and Jentic returns the matching Refuge Restrooms 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 API title use?

The API title uses no authentication. 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 getv1restrooms with the API title?

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

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

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 getv1restrooms through Jentic?

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

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

The API title exposes 4 endpoints covering restrooms operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The Refuge Restrooms API exposes only read-only endpoints for listing and searching restrooms, including by location and by date, so you scope access by operation: import just the operations the agent needs, such as searching restrooms or listing them by location, and leave the rest out. An operation is available to the agent only if you include it.
