Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs/Customer
Customer logo

Customer APIs

3 APIs45 Endpoints1 Category

Categories

All3Marketing3

API Catalog

Customer.io API

Jentic publishes the only available OpenAPI specification for Customer.io API, keeping it validated and agent-ready. Customer.io is a marketing automation platform that combines behavioural messaging, segmentation, and transactional email into a single workflow tool. This API surface covers customer identification and lifecycle, event tracking, device management, segment and campaign listing, newsletter metrics, customer and delivery exports, and transactional email sending. Authentication uses HTTP Basic with a site ID and API key pair.

21 endpoints

Customer.io Track API

Jentic publishes the only available OpenAPI specification for Customer.io Track API, keeping it validated and agent-ready. The Track API is the data ingestion surface for Customer.io, used to add and update people, record events, manage devices, suppress profiles, submit forms, merge duplicates, and send batched requests. It also includes account region discovery and a v2 entity endpoint for unified ingestion. Authentication uses HTTP Basic with a site ID and tracking API key.

16 endpoints

Customer.io Track API

Jentic publishes the only available OpenAPI specification for Customer.io Track API, keeping it validated and agent-ready. This focused Track API surface covers customer identification and lifecycle, event tracking (attributed and anonymous), device registration, and suppression management. It is the minimal ingestion layer for sending behavioural data into Customer.io to drive messaging campaigns. Authentication uses HTTP Basic with a site ID and tracking API key.

8 endpoints

Connect Your Agent

1

Step 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 | sh
2

Step 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 instance

Jentic 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.