Swagger da API responsável pela construção e operações da tela de lances. The API exposes 2 endpoints secured with oauth2 authentication.
2 endpointsSwagger da API responsável pelo gerenciamento de lances. The API exposes 7 endpoints secured with oauth2 authentication.
7 endpointsswagger das apis de coletores de editais. The API exposes 9 endpoints secured with oauth2 authentication.
9 endpointsSwagger da API responsável pela configuração de clientes. The API exposes 27 endpoints secured with oauth2 authentication.
27 endpointsSwagger da API responsável pela filtragem de editais. The API exposes 7 endpoints secured with oauth2 authentication.
7 endpointsSwagger da API responsável pelo gerenciamento das propostas. The API exposes 27 endpoints secured with oauth2 authentication.
27 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.