canonical: https://jentic.com/apis/swaggerhub.gmacem/bgk-info-handler

# Gmacem BGK info handler

This API to get order information for BGK customer. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically get order information. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get order information
- Manage e commerce data programmatically
- Integrate BGK info handler into automated workflows
- Query and filter BGK info handler records by parameters
- Monitor BGK info handler operational status and events

## Use cases

### E-Commerce Operations

Use the BGK info handler to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including get order information.

Example prompt: Call GET `/api/bgk/v1/order/info` to get order information

### Data Retrieval and Monitoring

Query BGK info handler 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 BGK info handler endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call BGK info handler 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 bearer tokens manually.

Example prompt: Search Jentic for 'get order information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/bgk/v1/order/info` | Get order information |

## Key resources

- **Bgk** — Operations for bgk

## Why Jentic

- **Setup:** Wiring the BGK info handler by hand means implementing its bearer JWT auth, pointing at the b2b-authproxy.taxi.yandex.net host, and handling token refresh and retries yourself. Through Jentic you install once, import the BGK info handler from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API exposes a single read operation, GET `/api/bgk/v1/order/info`, with its target in the request, so scoping is operations-only: you limit the agent to the operations it needs, such as reading order info, and no write path is exposed. Every operation you allow is one you have explicitly chosen.
- **Credential handling:** Your BGK info handler token 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 'get order information', and Jentic returns the matching BGK info handler operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the BGK info handler use?

The BGK info handler uses a Bearer token in the Authorization header. 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 order information with the BGK info handler?

Yes. Use the GET `/api/bgk/v1/order/info` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BGK info handler?

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 order information through Jentic?

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

### How many endpoints does the BGK info handler have?

The BGK info handler exposes 1 endpoints covering bgk operations.

### Can I limit what my agent is allowed to do with the BGK info handler API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The BGK info handler exposes a single read operation, GET `/api/bgk/v1/order/info`, so you scope by operation: you allow the agent to read order information and nothing else, and there is no write path to expose. Every operation the agent can call is one you have explicitly permitted.