Install Jentic One Beta

Connect the Flotiq User API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flotiq User 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%2Fflotiq.com%2Fflotiq" | sh

Step 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%2Fflotiq.com%2Fflotiq" | 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.

Capabilities

What an agent can do with Flotiq User API.

Retrieve the structured content objects defined in a Flotiq account

Add a content object or update selected fields with a patch

Apply batch create, update, and delete across many objects in one request

Upload and organise media objects

Tag content and list objects by tag

GET STARTED

Start building with Flotiq User API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Flotiq User API for, with concrete tasks.

★ Agent content retrieval and publishing

An AI agent connected through Jentic reads the structured content objects in a Flotiq account to answer a question, then creates or patches an object to publish an update, so a site or app stays current without the developer hand-wiring the auth token or the per-type request shapes.

Create a new content object in a Flotiq account and patch a selected field on an existing one

Bulk content migration

A migration tool moves a large set of records into Flotiq by posting them through the batch create endpoint and applies corrections with batch update, so thousands of objects land in a few calls instead of one request per record.

Create a batch of content objects in one request and apply a batch update to fix a field across them

Content versioning and audit

A governance workflow lists every version of a content object and fetches an earlier one to compare, and reads the removed-object identifiers to reconcile deletions, so an external search index mirrors the Flotiq account accurately.

List the versions of a content object, fetch an earlier version, and read the removed-object identifiers to reconcile an index

Key Endpoints

72 endpoints — the flotiq user api is a headless cms surface that serves the structured content objects, media, and tags defined in a flotiq account.

METHOD

PATH

DESCRIPTION

GET

/api/v1/content/_media

List media objects

POST

/api/v1/content/_media

Create a media object

GET

/api/v1/content/_media/{id}

Get a media object by id

PUT

/api/v1/content/_media/{id}

Update a media object

GET

/api/v1/content/_tag

List tag objects

POST

/api/v1/content/project/batch

Create a batch of objects

GET

/api/v1/content/project/{id}/version

List every version of an object

GET

/api/v1/content/_media/removed

Get removed object identifiers

GET

/api/v1/content/_media

List media objects

POST

/api/v1/content/_media

Create a media object

GET

/api/v1/content/_media/{id}

Get a media object by id

PUT

/api/v1/content/_media/{id}

Update a media object

GET

/api/v1/content/_tag

List tag objects

POST

/api/v1/content/project/batch

Create a batch of objects

GET

/api/v1/content/project/{id}/version

List every version of an object

GET

/api/v1/content/_media/removed

Get removed object identifiers

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Flotiq by hand means handling its X-AUTH-TOKEN header, learning the per-type content paths, and choosing between single-object and batch write flows yourself. Through Jentic you install once, import Flotiq from the API Directory, store the token once, and your agent calls it.

Permission scoping

Flotiq puts the content type and object id in the URL path (/api/v1/content/{type}/{id}), so a rule can pin your agent to read-only access on one content type. You choose the operations it may call, so write operations like batch delete or patching an object are not included unless you add them.

Credential isolation

Your Flotiq token 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 'create a content object' or 'list every version of an object', and Jentic returns the matching Flotiq operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Flotiq User API through Jentic.

What authentication does the Flotiq User API use?

The Flotiq User API reads a personal auth token from the `X-AUTH-TOKEN` header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's context.

Is there a Flotiq MCP server?

You don't need an MCP server to give your agent Flotiq. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the content read, write, and batch operations on demand, without a separate server's tool definitions loaded into its context.

Can I limit what my agent is allowed to do with the Flotiq User API?

Yes. Flotiq puts the content type and object id in the URL path, so a rule can pin your agent to read-only access on one content type, letting it fetch objects but not patch them, run a batch delete, or touch media, with every call logged.

Can I update content in batches with the Flotiq User API?

Yes. Each content type exposes batch create, batch update, and batch delete endpoints, so you can write or remove many objects in a single request rather than one call per record.

What are the rate limits for the Flotiq User API?

The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://flotiq.com for current limits before running large batch imports.

How do I publish a content object through Jentic?

Search Jentic for 'create a content object', which returns the Flotiq create operation with its input schema, then post the object and patch any field you need to change. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Flotiq User API

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent ManagementapiKey72 EndpointsREST

For Agents

Read and write the structured content objects, media, and tags in a Flotiq account, one at a time or in batches, with partial patches, full version history, and removed-object identifiers.

Use for: List the content objects in my Flotiq account, Create a new content object, Update selected fields of a content object, Upload a media object

Not supported: Does not handle page rendering, user authentication, or payment. Use for managing structured content objects and media in a Flotiq account only.

The Flotiq User API is a headless CMS surface that serves the structured content objects, media, and tags defined in a Flotiq account. It reads and writes each content object individually or in batches, applies partial updates by patching selected fields, and keeps a full version history so an earlier state of an object can be fetched or audited. It also lists the identifiers of removed objects, so a downstream index can reconcile deletions rather than re-reading everything.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

17%

Example Density

How richly the API is illustrated with examples.

78%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

63%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Flotiq User API to your agent

Capabilities

Start building with Flotiq User API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Flotiq User API

Jentic AI Readiness Score

Flotiq User API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness