Swaggerquiputech API Mpos
Browse all Swaggerhub Swaggerquiputech APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlbasic3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically initdevice, getterminal. Covers 3 operations with basic authentication.
Use for: I need to initdevice, I want to getterminal, Search for validatecard, List all records from API Mpos
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
MPos related operations. The API exposes 3 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the API Mpos to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Mpos, 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.swaggerquiputech%2Fapi-mpos" | 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.swaggerquiputech%2Fapi-mpos" | 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 API Mpos API.
InitDevice
GetTerminal
ValidateCard
Query and filter API Mpos records by parameters
Monitor API Mpos operational status and events
Use Cases
Patterns agents use API Mpos API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'initdevice', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — mpos related operations.
METHOD
PATH
DESCRIPTION
POST
/init/device
InitDevice
GET
/terminal/mpos/{serialNumber}
GetTerminal
POST
/validate/card
ValidateCard
POST
/init/device
InitDevice
GET
/terminal/mpos/{serialNumber}
GetTerminal
POST
/validate/card
ValidateCard
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
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 API Mpos API through Jentic.
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.
GET STARTED