canonical: https://jentic.com/apis/swaggerhub.coria9404-1/api-de-gestin-de-pases

# Coria9404 1 Country Management API

An API to retrieve, add, edit, and delete countries. The API exposes 4 endpoints.

## For AI agents

Programmatically access Country Management API resources. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for country management only.

## Capabilities

- Access Country Management API resources via REST API
- Manage country data programmatically
- Integrate Country Management API into automated workflows
- Query and filter Country Management API records by parameters
- Monitor Country Management API operational status and events

## Use cases

### Country Management Operations

Use the Country Management API to perform country management operations programmatically. The API provides 4 endpoints covering core functionality including retrieving all countries, adding a new country, editing a country by ID.

Example prompt: Execute a primary operation against the Country Management API

### Automated Country Workflows

Automate country operations by combining multiple Country Management API endpoints. Agents can add a new country and then edit a country by ID in a single workflow.

Example prompt: Add a new country and then update it via the Country Management API

### AI Agent Integration via Jentic

AI agents discover and call Country Management 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 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/pais` | Get all countries |
| POST | `/paisAgregar` | Agregar un país |
| PUT | `/paisEditar{paisId}` | Edit a country by ID |
| DELETE | `/paisEliminar{paisId}` | Delete a country by ID |

## Key resources

- **Countries** — Operations related to countries
- **Add Country** — Operations related to adding countries
- **Edit Country** — Operations related to editing countries
- **Delete Country** — Operations related to deleting countries

## Why Jentic

- **Setup:** Wiring the Country Management API by hand means pointing at its SwaggerHub mock host, matching the add, edit, and delete request formats, and handling responses yourself even though it takes no auth. Through Jentic you install once, import the Country Management API from the API Directory, store any connection detail once, and your agent calls it.
- **Permission scoping:** This API carries the country id in the URL path for edit and delete, so a rule can pin your agent to reading countries: you choose the operations it may call, so write operations like adding, editing, or deleting a country are not included unless you add them.
- **Credential handling:** Any Country Management API connection detail 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 countries' or 'add a country', and Jentic returns the matching Country Management 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 Country Management API use?

The Country Management API uses none 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.

### What are the rate limits for the Country Management 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 use country management API through Jentic?

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

### How many endpoints does the Country Management API have?

The Country Management API exposes 4 endpoints covering countries operations.

### Does the Country Management API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which Country Management API operations and connection details your agent may use. You can pin the agent to reading data by allowing only the get-all-countries call, so the write operations that add, edit, or delete a country stay off limits unless you explicitly grant them. Since edit and delete carry the country id in the URL path, you keep full control over whether the agent can ever change or remove a record.