Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the company.proto, 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.demo66%2Fcompanyproto" | shStep 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.demo66%2Fcompanyproto" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with company.proto API.
AddCompany
GetCompany
UpdateCompany
DeleteCompany
ListCompanies
Patterns agents use company.proto API for, with concrete tasks.
GET STARTED
★ 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.
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.
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.
Search Jentic for 'addcompany', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — swaggerhub.
METHOD
PATH
DESCRIPTION
/v1/companies
AddCompany
/v1/companies
GetCompany
/v1/companies
UpdateCompany
/v1/companies
DeleteCompany
/v1/companies/list
ListCompanies
/v1/companies
AddCompany
/v1/companies
GetCompany
/v1/companies
UpdateCompany
/v1/companies
DeleteCompany
/v1/companies/list
ListCompanies
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using company.proto API through Jentic.
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.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically addcompany, getcompany. Covers 5 operations.
Use for: I need to addcompany, I want to getcompany, Search for updatecompany, Find all deletecompany
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
swaggerhub.demo66/api version 1.0.0-ors3. The API exposes 5 endpoints.