canonical: https://jentic.com/apis/swaggerhub.demo66/groupproto

# Demo66 group.proto

swaggerhub.demo66/apigroup version 1.0.0-oas3. The API exposes 6 endpoints.

## For AI agents

Programmatically addgroup, getgroup. Covers 6 operations.

## Scope

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

## Capabilities

- AddGroup
- GetGroup
- UpdateGroup
- DeleteGroup
- GetAllGroup
- GetBySlug

## Use cases

### Developer Tools Operations

Use the group.proto to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including addgroup, getgroup, updategroup.

Example prompt: Call POST `/v1/groups` to addgroup

### Automated Groups Management

Automate groups operations by combining multiple group.proto endpoints. Agents can getgroup and then updategroup in a single workflow.

Example prompt: Call GET `/v1/groups` to getgroup, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call group.proto 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 'addgroup', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/groups` | AddGroup |
| GET | `/v1/groups` | GetGroup |
| PUT | `/v1/groups` | UpdateGroup |
| DELETE | `/v1/groups` | DeleteGroup |
| GET | `/v1/groups/list` | GetAllGroup |
| GET | `/v1/groups/slug` | GetBySlug |

## Key resources

- **Groups** — Operations for groups

## Why Jentic

- **Setup:** Wiring the group.proto API by hand means shaping its group create, read, update, delete, and list calls and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the group.proto API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API acts on a `/v1/groups` collection rather than per-resource paths, so scope by operation: limit the agent to what it needs, such as listing groups or looking one up by slug, and leave out delete unless you want it to remove records.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a group' or 'find a group by slug', and Jentic returns the matching group.proto 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 group.proto use?

The group.proto 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 addgroup with the group.proto?

Yes. Use the POST `/v1/groups` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the group.proto?

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

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

### How many endpoints does the group.proto have?

The group.proto exposes 6 endpoints covering groups operations.

### Can I limit what my agent is allowed to do with the group.proto API?

Yes. Because you run Jentic One yourself, your own rules decide which group.proto operations the agent can call and which credentials it may use. This API acts on a single `/v1/groups` collection rather than per-resource paths, so you scope it by operation: allow read-only calls like GetAllGroup to list groups or GetBySlug to look one up, and grant AddGroup or UpdateGroup only if the agent needs to write. Leave DeleteGroup out unless you explicitly want the agent to remove records.