Coria9404 1 Country Management API
Browse all Swaggerhub Coria9404 1 APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access Country Management API resources. Covers 4 operations.
Use for: I need to integrate with Country Management API, Find available country management operations, Get the current status of Country Management API resources, List all records from Country Management API
Not supported: Does not handle payments, communications, or crm - use for country management only.
An API to retrieve, add, edit, and delete countries. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the Country Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Country Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.coria9404-1%2Fapi-de-gestin-de-pases" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.coria9404-1%2Fapi-de-gestin-de-pases" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Country Management API.
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
Patterns agents use Country Management API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'country management API', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — an api to retrieve, add, edit, and delete countries.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Country Management API through Jentic.
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.
GET STARTED