canonical: https://jentic.com/apis/roadgoat.com/roadgoat-cities-api

# RoadGoat Cities API

The RoadGoat Cities API provides access to city and destination content including descriptions, photos, known-for tags, budget information, safety scores, and related destinations. It follows the JSON:API specification and provides rich data about cities worldwide for travel applications. The API exposes 3 endpoints secured with basic authentication.

## For AI agents

Programmatically search destinations, get destination by id. Covers 3 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Search Destinations
- Get Destination by ID
- Auto-Complete Destinations
- Query and filter RoadGoat Cities API records by parameters
- Monitor RoadGoat Cities API operational status and events

## Use cases

### Media and Content Operations

Use the RoadGoat Cities API to perform media operations programmatically. The API provides 3 endpoints covering core functionality including search destinations, get destination by id, auto-complete destinations.

Example prompt: Call GET /destinations to search destinations

### Automated Destinations Management

Automate destinations operations by combining multiple RoadGoat Cities API endpoints. Agents can get destination by id and then auto-complete destinations in a single workflow.

Example prompt: Call GET `/destinations/{id}` to get destination by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RoadGoat Cities 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/destinations` | Search Destinations |
| GET | `/destinations/{id}` | Get Destination by ID |
| GET | `/destinations/auto_complete` | Auto-Complete Destinations |

## Key resources

- **Destinations** — Search and retrieve city/destination information

## 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:** 40 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/roadgoat.com/roadgoat-cities-api/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 the RoadGoat Cities API by hand means setting up HTTP Basic auth with your API key as the username and secret as the password, sending it on every call to the roadgoat.com v2 host, and handling each destinations lookup yourself. Through Jentic you install once, import the RoadGoat Cities API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** RoadGoat puts the destination id in the URL path (`/destinations/{id}`), so a rule can pin your agent to one destination and its lookups. You choose the operations it may call, and since this API is read-only the agent searches and reads destinations without any write path unless you add one.
- **Credential handling:** Your RoadGoat API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search destinations' or 'get a destination by id', and Jentic returns the matching RoadGoat Cities API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the RoadGoat Cities API use?

The RoadGoat Cities API uses HTTP Basic authentication with username and password. 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 search destinations with the RoadGoat Cities API?

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

### What are the rate limits for the RoadGoat Cities 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 search destinations through Jentic?

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

### How many endpoints does the RoadGoat Cities API have?

The RoadGoat Cities API exposes 3 endpoints covering destinations operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which RoadGoat operations the agent may call and which credentials it may use. You can allow only the read operations you want, such as searching destinations with GET /destinations, looking one up with GET `/destinations/{id}`, or auto-completing with GET `/destinations/auto_complete`, and because this API is read-only there is no write path for the agent to take. Since the destination id sits in the URL path, a rule can also pin the agent to a single destination and its lookups.