Install Jentic One Beta

Connect the BGK info handler to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BGK info handler, 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.

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.gmacem%2Fbgk-info-handler" | sh

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.gmacem%2Fbgk-info-handler" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 BGK info handler API.

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

GET STARTED

Start building with BGK info handler API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

1 endpoints — this api to get order information for bgk customer.

METHOD

PATH

DESCRIPTION

GET

/api/bgk/v1/order/info

Get order information

GET

/api/bgk/v1/order/info

Get order information

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using BGK info handler API through Jentic.

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.

Gmacem BGK info handler

Name: BGK info handler API
Brand: BGK info handler
Availability: InStock

Browse all Swaggerhub Gmacem APIs

Community OpenAPI document · agent-readyE CommerceStorefrontbearer1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to order information, Find available e commerce operations, Get the current status of BGK info handler resources, List all records from BGK info handler

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

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

Jentic One on Github View OpenAPI Document

Connect the BGK info handler to your agent

Capabilities

Start building with BGK info handler API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Gmacem BGK info handler