Curfex integration API for business partner. This is a v2 version (released on 2022) replacing existing production version [Curfex API v1](https://app.swaggerhub.com/apis/curfex/curfex_api_v1). All listed APIs are [rate limited](https://www.notion.so/curfex/Rate-Limiting-def3bf1a33e345c4b34580ea282f3deb) Please contact us at tech@curfex.com if you need any help. The API exposes 27 endpoints secured with bearer authentication.
27 endpointsCurfex integration API for business partner. This is a v2 version (released on 2022) replacing existing production version [Curfex API v1](https://app.swaggerhub.com/apis/curfex/curfex_api_v1). All listed APIs are [rate limited](https://www.notion.so/curfex/Rate-Limiting-def3bf1a33e345c4b34580ea282f3deb) Please contact us at tech@curfex.com if you need any help. The API exposes 27 endpoints secured with bearer authentication.
27 endpointsStep 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.waikit-1" | 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.waikit-1" | 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.