canonical: https://jentic.com/apis/swaggerhub.visanet/swaggerhub-visanet

# Visanet MPos POS Servicios

MPos POS Servicios API. The API exposes 3 endpoints.

## For AI agents

Programmatically get functions for a terminal id, post-terminal-by-terminalid-functions-by-functionid. Covers 3 operations.

## Scope

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

## Capabilities

- Get functions for a Terminal Id
- post-terminal-by-terminalid-functions-by-functionid
- Integrate MPos POS Servicios into automated workflows
- Query and filter MPos POS Servicios records by parameters
- Monitor MPos POS Servicios operational status and events

## Use cases

### Developer Tools Operations

Use the MPos POS Servicios to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including get functions for a terminal id, post-terminal-by-terminalid-functions-by-functionid, get function definition for a terminal id.

Example prompt: Call GET `/terminal/{terminalId}/functions` to get functions for a terminal id

### Automated terminal Management

Automate terminal operations by combining multiple MPos POS Servicios endpoints. Agents can post-terminal-by-terminalid-functions-by-functionid and then get function definition for a terminal id in a single workflow.

Example prompt: Call POST `/terminal/{terminalId}/functions/{functionId}` to post-terminal-by-terminalid-functions-by-functionid, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call MPos POS Servicios 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 'get functions for a terminal id', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/terminal/{terminalId}/functions` | Get functions for a Terminal Id |
| POST | `/terminal/{terminalId}/functions/{functionId}` | post-terminal-by-terminalid-functions-by-functionid |
| GET | `/terminal/{terminalId}/functions/{functionId}` | Get function definition for a Terminal Id |

## Key resources

- **terminal** — Operations related to terminal

## Why Jentic

- **Setup:** Wiring MPos POS Servicios by hand means pointing at its api.posservicios.quiputech.com host, handling its open (no-auth) access, and coding its terminal-function calls yourself. Through Jentic you install once, import MPos POS Servicios from the API Directory, store any needed config once, and your agent calls it.
- **Permission scoping:** MPos POS Servicios puts the terminal id in the URL path (`/terminal/{terminalId}/functions/...`), so a rule can pin your agent to one terminal: it can list and read functions for that terminal and nothing else. You choose the operations it may call, so activating a function with POST `/terminal/{terminalId}/functions/{functionId}` is not included unless you add it.
- **Credential handling:** This API requires no credential, and any config your setup needs 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 functions for a terminal' or 'read a terminal function', and Jentic returns the matching MPos POS Servicios 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 MPos POS Servicios use?

The MPos POS Servicios 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 get functions for a terminal id with the MPos POS Servicios?

Yes. Use the GET `/terminal/{terminalId}/functions` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the MPos POS Servicios?

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 get functions for a terminal id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get functions for a terminal id'. Jentic returns the matching MPos POS Servicios operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the MPos POS Servicios have?

The MPos POS Servicios exposes 3 endpoints covering terminal operations.

### Can I limit what my agent is allowed to do with the MPos POS Servicios API?

Yes. Because you run Jentic One yourself, your own rules decide which MPos POS Servicios operations and credentials the agent may use. Since the terminal id sits in the URL path, you can pin the agent to a single terminal and grant only the read operations, so it lists functions with GET `/terminal/{terminalId}/functions` and reads a definition with GET `/terminal/{terminalId}/functions/{functionId}` and nothing else. Activating a function with POST `/terminal/{terminalId}/functions/{functionId}` stays blocked unless you explicitly allow it.