Jentic publishes the only available OpenAPI specification for CRM cards, keeping it validated and agent-ready. The HubSpot CRM cards API lets developer apps extend the CRM record sidebar by registering custom cards that pull data from external systems when a user opens a contact, company, or deal record. Cards are configured up-front per app and populated at view time by an external data fetch URL the app exposes. This is the building block for embedding third-party context — order history, support tickets, billing — directly in the HubSpot CRM UI.
6 endpointsJentic publishes the only available OpenAPI specification for HubSpot CRM Cards, keeping it validated and agent-ready. The CRM Cards API lets a HubSpot app extend the CRM UI by surfacing custom cards in the sidebar of contact, company, deal, and ticket record pages. Apps register card definitions up front, including the data fetch URL HubSpot calls when a record loads. The card definitions, sample-response shape, and per-app card list are all managed through this API.
6 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.