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

# Demo66 company.proto

swaggerhub.demo66/api version 1.0.0-ors3. The API exposes 5 endpoints.

## For AI agents

Programmatically addcompany, getcompany. Covers 5 operations.

## Scope

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

## Capabilities

- AddCompany
- GetCompany
- UpdateCompany
- DeleteCompany
- ListCompanies

## Use cases

### Developer Tools Operations

Use the company.proto to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including addcompany, getcompany, updatecompany.

Example prompt: Call POST `/v1/companies` to addcompany

### Automated Companies Management

Automate companies operations by combining multiple company.proto endpoints. Agents can getcompany and then updatecompany in a single workflow.

Example prompt: Call GET `/v1/companies` to getcompany, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/companies` | AddCompany |
| GET | `/v1/companies` | GetCompany |
| PUT | `/v1/companies` | UpdateCompany |
| DELETE | `/v1/companies` | DeleteCompany |
| GET | `/v1/companies/list` | ListCompanies |

## Key resources

- **Companies** — Operations for companies

## Why Jentic

- **Setup:** Wiring the company.proto API by hand means shaping its company create, read, update, delete, and list calls and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the company.proto API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API acts on a `/v1/companies` collection rather than per-resource paths, so scope by operation: limit the agent to what it needs, such as listing and reading companies, 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 company' or 'list companies', and Jentic returns the matching company.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 company.proto use?

The company.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 addcompany with the company.proto?

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

### What are the rate limits for the company.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 addcompany through Jentic?

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

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

The company.proto exposes 5 endpoints covering companies operations.

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

Yes. Because Jentic One is self-hosted, you decide which of the company.proto operations your agent may call, and your own rules are enforced at execution time. Since this API works against a single `/v1/companies` collection rather than per-record paths, you scope by operation: for example, allow AddCompany, GetCompany, and ListCompanies while leaving out DeleteCompany so the agent can create and read records but never remove them. This API needs no credentials, so the only thing you control is the set of operations the agent is permitted to run.