canonical: https://jentic.com/apis/swaggerhub.gmf-tech/api-bid

# Gmf Tech API Bid

Swagger da API responsável pelo gerenciamento de lances. The API exposes 7 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically lista de pregões do dia atual | scope-> bid:read, consultar pregão específico | scope-> bid:read. Covers 7 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Lista de pregões do dia atual | scope-> bid:read
- Consultar pregão específico | scope-> bid:read
- Atualiza informações de lances | scope-> bid:write
- Envia log de uma sessão de lances | scope-> bid:write
- Reportar incidente para equipe de suporte | scope-> bid:write

## Use cases

### Developer Tools Operations

Use the API Bid to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including lista de pregões do dia atual | scope-> bid:read, consultar pregão específico | scope-> bid:read, atualiza informações de lances | scope-> bid:write.

Example prompt: Call GET /bids/today/{customer} to lista de pregões do dia atual | scope-> bid:read

### Automated Bids Management

Automate bids operations by combining multiple API Bid endpoints. Agents can consultar pregão específico | scope-> bid:read and then atualiza informações de lances | scope-> bid:write in a single workflow.

Example prompt: Call GET /bid/{identifier} to consultar pregão específico | scope-> bid:read, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Bid 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'lista de pregões do dia atual | scope-> bid:read', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /bids/today/{customer} | Lista de pregões do dia atual \| scope-> bid:read |
| GET | /bid/{identifier} | Consultar pregão específico \| scope-> bid:read |
| PUT | /bid/{identifier} | Atualiza informações de lances \| scope-> bid:write |
| PUT | /bid/closure/{identifier} | Atualiza informações de itens encerrados \| scope-> bid:write |
| PUT | /bid/log/{identifier} | Envia log de uma sessão de lances \| scope-> bid:write |
| PUT | /bid/help | Reportar incidente para equipe de suporte \| scope-> bid:write |
| PUT | /bid/issue/{identifier} | Reportar incidente relacionado à uma sessão de lances \| scope-> bid:write |

## Key resources

- **Bids** — Gerenciamento de lances
- **Issue report** — Reportar ocorrências
- **Logs** — Gerenciamento de logs de lances

## Why Jentic

- **Setup:** Wiring the Bidbr API Bid service by hand means running its OAuth2 password flow against api-login.bidbr.com.br, mapping the right ACL scopes, and handling token refresh and retries yourself. Through Jentic you install once, import API Bid from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** This API puts the bid identifier in the URL path (/bid/{identifier}), so a rule can pin your agent to one bid: it can read and update that bid and nothing else. You choose the operations it may call, so destructive ones like bid closure are not included unless you add them.
- **Credential handling:** Your API Bid OAuth2 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 'update a bid by identifier' or 'list today's bids for a customer', and Jentic returns the matching API Bid 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 Bid use?

The API Bid uses OAuth 2.0 for authorization. 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 lista de pregões do dia atual | scope-> bid:read with the API Bid?

Yes. Use the GET /bids/today/{customer} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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 lista de pregões do dia atual | scope-> bid:read through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'lista de pregões do dia atual | scope-> bid:read'. Jentic returns the matching API Bid operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The API Bid exposes 7 endpoints covering bids, issue report, logs operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which API Bid operations and credentials the agent may use, so you can allow only reads like GET /bids/today/{customer} and GET /bid/{identifier} while withholding writes such as PUT /bid/{identifier} or PUT /bid/closure/{identifier}. Since the bid identifier sits in the URL path, a rule can pin the agent to a single bid, letting it read and update that one bid and nothing else. Destructive operations like bid closure are excluded unless you explicitly grant them.