canonical: https://jentic.com/apis/swaggerhub.swaggerquiputech/api-mpos

# Swaggerquiputech API Mpos

MPos related operations. The API exposes 3 endpoints secured with basic authentication.

## For AI agents

Programmatically initdevice, getterminal. Covers 3 operations with basic authentication.

## Scope

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

## Capabilities

- InitDevice
- GetTerminal
- ValidateCard
- Query and filter API Mpos records by parameters
- Monitor API Mpos operational status and events

## Use cases

### Developer Tools Operations

Use the API Mpos to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including initdevice, getterminal, validatecard.

Example prompt: Call POST /init/device to initdevice

### Automated MPos API Management

Automate mpos API operations by combining multiple API Mpos endpoints. Agents can getterminal and then validatecard in a single workflow.

Example prompt: Call GET /terminal/mpos/{serialNumber} to getterminal, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Mpos 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 'initdevice', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /init/device | InitDevice |
| GET | /terminal/mpos/{serialNumber} | GetTerminal |
| POST | /validate/card | ValidateCard |

## Key resources

- **MPos Api** — RESTful API for MPos operations
- **MPos Init Api** — RESTful API for Init operations
- **MPos Terminal Api** — RESTful API for Terminal operations

## Why Jentic

- **Setup:** Wiring API Mpos by hand means handling its basic auth, targeting the mPOS host, and managing device init, terminal lookup, and card validation calls and retries yourself. Through Jentic you install once, import API Mpos from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** API Mpos takes most of its targets in the request body, so scope the agent to the operations it needs, such as initializing a device or validating a card. You choose which operations it may call, so anything you leave out stays unavailable to the agent.
- **Credential handling:** Your API Mpos basic credentials 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 'initialize an mPOS device' or 'validate a card', and Jentic returns the matching API Mpos 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 Mpos use?

The API Mpos 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 initdevice with the API Mpos?

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

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

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

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

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

The API Mpos exposes 3 endpoints covering mpos API, mpos init API, mpos terminal API operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which API Mpos operations and credentials the agent may use. API Mpos takes most of its targets in the request body, so you can scope the agent to only the operations it needs, such as initializing a device or validating a card, while leaving out terminal lookup. Any operation you do not grant stays unavailable to the agent.