Apideck CRM is a unified API that maps a single schema for companies, contacts, leads, opportunities, pipelines, activities, notes, and users onto downstream CRMs such as Salesforce, HubSpot, Pipedrive, Zoho, and Microsoft Dynamics. The 40 operations cover the day-to-day CRM objects most apps need, and Apideck routes each call through Apideck Vault so per-customer CRM credentials never reach the calling app. Builders typically replace 5+ direct CRM integrations with a single Apideck contract.
40 endpointsApideck Customer Support is a unified API that maps a single customer schema onto downstream support platforms such as Zendesk, Freshdesk, Intercom, and HubSpot Service Hub. The 9.5.0 spec is intentionally narrow: 5 operations focused on the customer object, so a SaaS app can pull or push customer records through one integration regardless of which help desk the end user runs. Apideck routes each call through Apideck Vault so per-customer help-desk credentials never reach the calling app.
5 endpointsThe Apideck Lead API is a focused unified interface for working with sales leads across CRMs and lead-capture tools including Salesforce, HubSpot, Pipedrive, and Zoho. Five endpoints cover the full CRUD lifecycle on a single normalised lead resource — list, create, get, update, and delete — so a marketing form, chat widget, or AI agent can push qualified leads into whichever CRM the customer uses without per-vendor code. Authentication uses the standard Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id.
5 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.