Install Jentic One Beta

Connect the Markifact API to your agent

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

List the connection types Markifact supports, with their auth methods and the credential fields each manual type expects

Create a connection from existing credentials, verified with the provider before it is stored

Generate a shareable OAuth auth link for an OAuth-only connection type and poll whether it is pending, connected, or expired

Look up a connection by Markifact connection ID or by your own external_id using lookup_by

GET STARTED

Start building with Markifact API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Markifact API for, with concrete tasks.

★ Client onboarding agent through Jentic

An agency assistant connects each new client's accounts to the Markifact workspace. Through Jentic it lists connection types, creates an auth link tagged with the client's external_id, sends it, and polls the link's status until it is connected. The Markifact bearer token is injected by Jentic at call time, so the agent never sees it.

GET /v1/connections/types, then POST /v1/connections/auth-link with connection_type set to the chosen type, external_id 'client-42', and redirect_url 'https://agency.example.com/done', and poll GET /v1/connections/auth-links/{auth_link_id}/status until it reports connected

Connecting accounts from existing credentials

When the team already holds a provider credential, a connection can be created directly for any type whose auth_methods include manual. Markifact checks the credentials with the provider first, so a successful response means the connection works. OAuth-only types cannot be created this way and need an auth link instead.

POST /v1/connections with connection_type, name 'Client 42 account', and the credentials fields listed for that type by GET /v1/connections/types

Credit spend reporting

Teams running Markifact workflows, agents, and copilot need to see where credits go. The credit balance call returns the current balance, and the credit log lists charges newest first, filterable by service_type, service_id, user_id, and a created_after and created_before window in Unix seconds.

GET /v1/credits, then GET /v1/credits/logs with service_type 'workflow' and created_after set to seven days ago, and total the charges per service_id

Troubleshooting failed runs

When a workflow misbehaves, operation logs show what ran. Logs can be filtered by source_type, status such as error, operation_id, source_id, and source_run_id for a single workflow run, and one log can be fetched by ID for full detail.

GET /v1/logs with source_type 'workflow' and status 'error', then GET /v1/logs/{log_id} for the newest entry and summarise what failed

Key Endpoints

11 endpoints — the markifact api manages the external account connections in a markifact team workspace and reports what the team's workflows and agents have run and spent.

METHOD

PATH

DESCRIPTION

GET

/v1/connections/types

List connection types

POST

/v1/connections

Create a connection from credentials

POST

/v1/connections/auth-link

Create an OAuth auth link

GET

/v1/connections/auth-links/{auth_link_id}/status

Check auth link status

GET

/v1/connections

List connections

GET

/v1/credits/logs

List credit charges

GET

/v1/logs

List operation logs

GET

/v1/connections/types

List connection types

POST

/v1/connections

Create a connection from credentials

POST

/v1/connections/auth-link

Create an OAuth auth link

GET

/v1/connections/auth-links/{auth_link_id}/status

Check auth link status

GET

/v1/connections

List connections

GET

/v1/credits/logs

List credit charges

GET

/v1/logs

List operation logs

Why Jentic?

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

Setup

Wiring Markifact by hand means managing its bearer token, choosing between manual credentials and OAuth auth links per connection type, and paging logs with next_cursor. Through Jentic you install once, import the Markifact API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Markifact puts the connection id in the URL path (/v1/connections/{connection_id}), so a rule can limit your agent to one connection and the operations you pick for it. You choose the operations it may call, so destructive ones like connection deletion or credential-based connection creation are not included unless you add them.

Credential isolation

Your Markifact 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 an OAuth link to connect an account' or 'list failed workflow logs', and Jentic returns the matching Markifact operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Markifact API through Jentic.

Is there a Markifact MCP server?

You don't need an MCP server to give your agent the Markifact API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Connection and log operations are found by intent when needed, so no extra tool definitions sit in the agent's context.

What authentication does the Markifact API use?

Per its OpenAPI spec, the Markifact API authenticates with a bearer token in the Authorization header. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

What is the difference between creating a connection and creating an auth link?

POST /v1/connections takes credentials you already hold and works only for connection types whose auth_methods include manual; Markifact verifies them with the provider before storing. POST /v1/connections/auth-link creates a shareable OAuth link for OAuth types, and its status endpoint reports pending, connected, or expired.

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

Yes. Write a rule that allows only GET /v1/logs, GET /v1/logs/{log_id}, and GET /v1/credits/logs, so a reporting agent can investigate runs and spend but cannot create or delete connections. Your own instance runs those calls.

What are the rate limits for the Markifact API?

The OpenAPI spec does not specify rate limits. Check the Markifact documentation at https://docs.markifact.com for current limits.

How do I send a client an OAuth connection link through Jentic?

Add the Markifact API to Jentic One from the directory and store your bearer token once. Your agent searches for 'create an OAuth link to connect an account', calls POST /v1/connections/auth-link with connection_type and an external_id, and later checks the link's status. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Markifact API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer11 EndpointsREST

For Agents

Connect external accounts to a Markifact workspace with credentials or OAuth auth links, look up and delete connections, and read credit balance, credit charges, and operation logs.

Use for: I need to connect a client's external account to our Markifact workspace, Send a client an OAuth link so they can connect their account, Check whether the auth link I sent has been connected yet, List all connections tagged with external ID client-42

Not supported: Does not build or run marketing workflows, publish ads, or send campaigns through this spec. Use for managing Markifact workspace connections, credits, and operation logs only.

The Markifact API manages the external account connections in a Markifact team workspace and reports what the team's workflows and agents have run and spent. Connections are created either from credentials you already hold, which Markifact verifies with the provider before storing, or through a shareable OAuth auth link whose status moves from pending to connected or expired. The same API returns the team's credit balance, a ledger of credit charges filterable by service_type, and operation logs filterable by source_type and status.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

35%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

48%

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: D+Signals: 4

46%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Markifact API to your agent

Capabilities

Start building with Markifact API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Markifact API

Jentic AI Readiness Score

Markifact 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