Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Taqtics 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%2Ftaqtics.co%2Ftaqtics" | 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%2Ftaqtics.co%2Ftaqtics" | 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 Taqtics API.
Create location
Search locations
Get location
Query and filter Taqtics API records by parameters
Monitor Taqtics API operational status and events
GET STARTED
Patterns agents use Taqtics API for, with concrete tasks.
★ Analytics Operations
Use the Taqtics API to perform analytics operations programmatically. The API provides 5 endpoints covering core functionality including create location, search locations, get location.
Call POST /locations to create location
Automated Locations Management
Automate locations operations by combining multiple Taqtics API endpoints. Agents can search locations and then get location in a single workflow.
Call GET /locations to search locations, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Taqtics 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 'create location', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — location intelligence and business analytics api.
METHOD
PATH
DESCRIPTION
/locations
Create location
/locations
Search locations
/locations/{locationId}
Get location
/analytics/demographics
Get demographic analytics
/analytics/footfall
Get footfall analytics
/locations
Create location
/locations
Search locations
/locations/{locationId}
Get location
/analytics/demographics
Get demographic analytics
/analytics/footfall
Get footfall analytics
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Taqtics API by hand means sending its X-API-Key header on every request, targeting the landmark.taqtics.co host, and building your own retry handling. Through Jentic you install once, import the Taqtics API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Taqtics API puts the location id in the URL path (/locations/{locationId}), so a rule can pin your agent to one location: it can read that location and pull its demographics and footfall analytics. You choose the operations it may call, so creating locations is not included unless you add it.
Credential isolation
Your Taqtics API 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 'get footfall analytics' or 'list locations', and Jentic returns the matching Taqtics API 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 Taqtics API through Jentic.
What authentication does the Taqtics API use?
The Taqtics API uses an API key passed in the `X-API-Key` header. 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 create location with the Taqtics API?
Yes. Use the POST /locations endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Taqtics 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 create location through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create location'. Jentic returns the matching Taqtics API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Taqtics API have?
The Taqtics API exposes 5 endpoints covering locations, analytics operations.
Can I limit what my agent is allowed to do with the Taqtics API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Taqtics API operations and credentials the agent may use. Because the location id sits in the URL path (/locations/{locationId}), you can pin the agent to a single location and let it read that location and pull its demographic and footfall analytics while blocking everything else. You pick the operations it may call, so creating locations with POST /locations stays off unless you explicitly allow it.
For Agents
Programmatically create location, search locations. Covers 5 operations with apiKey authentication.
Use for: I need to location, I want to locations, Search for location, Find all demographic analytics
Not supported: Does not handle payments, communications, or crm - use for analytics only.
Location intelligence and business analytics API. 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>