Jentic publishes the only available OpenAPI specification for Amazon Connect, keeping it validated and agent-ready. Amazon Connect is a cloud contact center service that handles voice, chat, tasks, and email interactions, contact routing, agent management, and real-time and historical analytics. The API surface covers instance configuration, contact flows, routing profiles, queues, hours of operations, agent statuses, contact controls (transfer, hold, monitor), Lex and Lambda integrations, predictive and outbound dialing, and storage for recordings and transcripts. It is the programmatic surface behind a complete enterprise contact center.
171 endpointsJentic publishes the only available OpenAPI specification for Amazon Connect Participant Service, keeping it validated and agent-ready. Amazon Connect Participant Service is the customer-side API for Amazon Connect chat sessions. Once a chat is started through Amazon Connect, the participant exchanges a participant token for a connection, then sends messages, posts events such as typing indicators, and uploads attachments through this API. It powers the customer half of every Amazon Connect chat experience.
8 endpointsJentic publishes the only available OpenAPI specification for Amazon Pinpoint Email Service, keeping it validated and agent-ready. Pinpoint Email is a transactional and bulk email sending service for AWS that supports verified sending identities, dedicated IP pools, configuration sets with event destinations, and a deliverability dashboard. The API exposes 42 operations covering identity verification, dedicated IP management, suppression list control, deliverability monitoring, and the SendEmail call itself. It serves teams that need programmatic control of email infrastructure with detailed reputation and deliverability telemetry.
42 endpointsJentic publishes the only available OpenAPI specification for Amazon Simple Email Service, keeping it validated and agent-ready. Amazon SES is AWS's high-throughput email sending and receiving service for transactional and marketing email. The API covers identity verification, configuration sets, custom verification email templates, dedicated IP pools, receipt rules, sending statistics, and DKIM and bounce handling. It is built for engineering teams that need to send high-volume email from their own domains with deliverability instrumentation rather than depend on third-party email gateways.
142 endpointsJentic publishes the only available OpenAPI specification for the API Gateway Management API, keeping it validated and agent-ready. The Amazon API Gateway Management API is the runtime companion to API Gateway WebSocket APIs. It exposes three operations on the @connections resource that let backends send messages to a connected WebSocket client, inspect connection metadata, and force a disconnect. Real-time chat services, live dashboards, and collaborative apps use it to push server-initiated messages to clients without client polling.
3 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.