Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Contaqt API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 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%2Fqliq.cloud%2Fqliq" | 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%2Fqliq.cloud%2Fqliq" | 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.
What an agent can do with Contaqt API.
Validate API key
Get articles
Add subscriber
Remove subscriber
Start automation flow
Patterns agents use Contaqt API for, with concrete tasks.
GET STARTED
★ Marketing Operations
Use the Contaqt API to perform marketing operations programmatically. The API provides 5 endpoints covering core functionality including validate API key, get articles, add subscriber.
Call POST /apis/checking-api-key to validate API key
Automated Articles Management
Automate articles operations by combining multiple Contaqt API endpoints. Agents can get articles and then add subscriber in a single workflow.
Call POST /articles/get-v2 to get articles, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Contaqt API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'validate API key', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — contaqt marketing api for managing articles, mailing list subscribers, and automation flows.
METHOD
PATH
DESCRIPTION
/apis/checking-api-key
Validate API key
/articles/get-v2
Get articles
/articles/add-subscriber-v2
Add subscriber
/articles/remove-subscriber-v2
Remove subscriber
/apis/start-flow
Start automation flow
/apis/checking-api-key
Validate API key
/articles/get-v2
Get articles
/articles/add-subscriber-v2
Add subscriber
/articles/remove-subscriber-v2
Remove subscriber
/apis/start-flow
Start automation flow
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Contaqt API by hand means passing your api_key on every query string and posting each article and flow call yourself. Through Jentic you install once, import the Contaqt API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Contaqt takes its article and subscriber details in the request body rather than as path resources, so scope the agent to the operations it needs, such as adding a subscriber or fetching articles. You choose that allowed set, so removing a subscriber or starting a flow is not included unless you add it.
Credential isolation
Your Contaqt key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'validate an API key' or 'add a subscriber to an article', and Jentic returns the matching Contaqt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Contaqt API through Jentic.
What authentication does the Contaqt API use?
The Contaqt API uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I validate API key with the Contaqt API?
Yes. Use the POST /apis/checking-api-key endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Contaqt API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I validate API key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate API key'. Jentic returns the matching Contaqt API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Contaqt API have?
The Contaqt API exposes 5 endpoints covering articles, authentication, flows operations.
Can I limit what my agent is allowed to do with the Contaqt API?
Yes. Because you run Jentic One yourself, your own rules decide which Contaqt operations and credentials the agent may use, so you grant only the calls it needs, such as fetching articles or adding a subscriber, while leaving out removing a subscriber or starting an automation flow. Contaqt takes its article and subscriber details in the request body rather than as path resources, so scoping is done at the operation level rather than per record. Your API key is stored encrypted by your Jentic One instance and injected only when an allowed operation runs, so it never enters the agent's prompt or logs.
For Agents
Programmatically validate API key, get articles. Covers 5 operations with apiKey authentication.
Use for: I need to validate API key, I want to articles, Search for add subscriber, Find all remove subscriber
Not supported: Does not handle payments, communications, or crm - use for marketing only.
Contaqt marketing API for managing articles, mailing list subscribers, and automation flows. The API exposes 5 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>