canonical: https://jentic.com/apis/swaggerhub.mobytelab/mock-api-for-driver-app

# Mobytelab MOCK API FOR DRIVER APP

This Mock API for user app. The API exposes 2 endpoints.

## For AI agents

Programmatically get-checkexistedaccount, get-getregisterlink. Covers 2 operations.

## Scope

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

## Capabilities

- get-checkexistedaccount
- get-getregisterlink
- Integrate MOCK API FOR DRIVER APP into automated workflows
- Query and filter MOCK API FOR DRIVER APP records by parameters
- Monitor MOCK API FOR DRIVER APP operational status and events

## Use cases

### Developer Tools Operations

Use the MOCK API FOR DRIVER APP to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including get-checkexistedaccount, get-getregisterlink.

Example prompt: Call GET /checkExistedAccount to get-checkexistedaccount

### Data Retrieval and Monitoring

Query MOCK API FOR DRIVER APP resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary MOCK API FOR DRIVER APP endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call MOCK API FOR DRIVER APP 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-checkexistedaccount', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/checkExistedAccount` | get-checkexistedaccount |
| GET | `/getRegisterLink` | get-getregisterlink |

## Key resources

- **Login** — Mocking Api for Login process
- **Register** — Mocking Api for Register process

## Why Jentic

- **Setup:** Wiring the driver-app mock API by hand means coding its account-check and register-link GET calls and handling retries yourself. Through Jentic you install once, import the driver-app API from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This API carries its inputs as query parameters rather than URL path ids, so scope the agent to the operations it needs, such as checking an existing account. You choose the operations it may call, so the register-link operation is not included unless you add it.
- **Credential handling:** Any access details for the driver-app API 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 'check whether an account exists' or 'get a registration link', and Jentic returns the matching driver-app 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 MOCK API FOR DRIVER APP use?

The MOCK API FOR DRIVER APP 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-checkexistedaccount with the MOCK API FOR DRIVER APP?

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

### What are the rate limits for the MOCK API FOR DRIVER APP?

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

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

### How many endpoints does the MOCK API FOR DRIVER APP have?

The MOCK API FOR DRIVER APP exposes 2 endpoints covering login, register operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which of the API's operations and credentials the agent may use. Because this API's inputs travel as query parameters rather than URL path ids, you scope the agent to just the operations it needs, such as the GET /checkExistedAccount call that checks whether an account already exists. The GET /getRegisterLink operation stays off-limits unless you explicitly add it to what the agent is permitted to call.