canonical: https://jentic.com/apis/taqtics.co/taqtics

# Taqtics API

Location intelligence and business analytics API. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create location, search locations. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create location
- Search locations
- Get location
- Query and filter Taqtics API records by parameters
- Monitor Taqtics API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create location', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/locations` | Create location |
| GET | `/locations` | Search locations |
| GET | `/locations/{locationId}` | Get location |
| POST | `/analytics/demographics` | Get demographic analytics |
| POST | `/analytics/footfall` | Get footfall analytics |

## Key resources

- **Locations** — Location data operations
- **Analytics** — Business analytics operations

## AI readiness

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.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/taqtics.co/taqtics/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

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