Install Jentic One Beta

Connect the Coppica API to your agent

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

Run a copywriting bot for a client as an async job and poll it for the output

Report a real-world outcome against a specific output so future copy is informed by it

Rank candidate outputs head-to-head to pick a winner

Diagnose which persuasion techniques a given output used

Extract persuasion techniques from arbitrary pasted copy

GET STARTED

Start building with Coppica API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Coppica API for, with concrete tasks.

★ Outcome-Driven Copy Generation

An agent runs a copywriting bot for a client, deploys the output, then reports the real conversion outcome back against that exact output so the next generation is grounded in what performed. Coppica ties outcomes to specific outputs, which closes the loop between the copy produced and the results it drove rather than generating blind.

Run a bot with POST /clients/{clientId}/bots/{botType}/run, poll GET /jobs/{outputId}, then report results with POST /outcomes

Candidate Ranking and Diagnosis

Before shipping, an agent ranks several candidate outputs head-to-head and diagnoses which persuasion techniques each relied on, so a marketer can pick the strongest variant with a reason. Coppica returns the ranking and a technique breakdown as structured data the agent can summarise.

Rank options with POST /clients/{clientId}/rank-outputs, then call POST /clients/{clientId}/outputs/{outputId}/diagnose on the winner

AI Agent Integration via Jentic

An AI agent reaches Coppica through Jentic without handling the API key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent generate and evaluate copy for a client inside a larger marketing workflow without managing the key in code.

Search Jentic for 'generate marketing copy for a client', load the POST /clients/{clientId}/bots/{botType}/run schema, and execute it with Jentic-managed credentials

Key Endpoints

58 endpoints — the coppica api generates persuasion-engineered marketing copy for a client, then takes real-world outcomes reported against each output so later generations learn from what actually converted.

METHOD

PATH

DESCRIPTION

POST

/clients/{clientId}/bots/{botType}/run

Run a copywriting bot as an async job

GET

/jobs/{outputId}

Poll a bot run

POST

/outcomes

Report an outcome against an output

POST

/clients/{clientId}/rank-outputs

Rank candidate outputs head-to-head

POST

/clients/{clientId}/outputs/{outputId}/diagnose

Diagnose which techniques an output used

POST

/extract

Extract persuasion techniques from arbitrary copy

POST

/clients/{clientId}/workflows

Run a multi-stage workflow

POST

/clients/{clientId}/bots/{botType}/run

Run a copywriting bot as an async job

GET

/jobs/{outputId}

Poll a bot run

POST

/outcomes

Report an outcome against an output

POST

/clients/{clientId}/rank-outputs

Rank candidate outputs head-to-head

POST

/clients/{clientId}/outputs/{outputId}/diagnose

Diagnose which techniques an output used

POST

/extract

Extract persuasion techniques from arbitrary copy

POST

/clients/{clientId}/workflows

Run a multi-stage workflow

Why Jentic?

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

Setup

Wiring Coppica by hand means managing its scoped bearer key, running bots as asynchronous jobs, and polling for each output before you can report an outcome. Through Jentic you install once, import Coppica from the API Directory, store the key once, and your agent calls it.

Permission scoping

Coppica puts the client id in the URL path (/clients/{clientId}/...), so a rule can pin your agent to one client: it can run bots and report outcomes for that client and nothing else. You choose which operations it may call, so destructive ones like graph-node or webhook deletion are not included unless you add them.

Credential isolation

Your Coppica 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 'generate marketing copy' or 'report a conversion outcome', and Jentic returns the matching Coppica operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Coppica API through Jentic.

What authentication does the Coppica API use?

The Coppica API authenticates with a bearer API key in the Authorization header, per its OpenAPI spec, using keys that carry read, write, and execute scopes. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

Can I report conversion outcomes with the Coppica API?

Yes. The outcomes operation records a real-world result against a specific output, which is the loop that lets later generations learn from what converted. You can also read an audit log of the outcomes a key has reported and the aggregated conversion performance for an output.

What are the rate limits for the Coppica API?

The OpenAPI spec does not publish specific rate-limit numbers; check https://coppica.com/docs/api for the current limits on your plan. The identity operation returns your plan and credit balance, so an agent can see how much generation headroom it has before running a batch of bots.

Is there a Coppica MCP server?

You don't need an MCP server to give your agent Coppica. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the bot-run and outcome operations. Nothing extra is loaded into the agent's context until an operation is actually invoked.

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

Yes. Coppica puts the client id in the URL path, so write a rule that pins your agent to one client and allows only the bot-run and outcome operations under it, leaving other clients and destructive campaign-graph edits out of reach. Every call runs through your own Jentic One instance and is logged for you to review.

How do I generate copy with the Coppica API through Jentic?

Search Jentic for 'generate marketing copy for a client', and it returns the Coppica bot-run operation with its input schema. Load the schema and execute POST /clients/{clientId}/bots/{botType}/run, then poll GET /jobs/{outputId}, with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Coppica API

AI ReadinessFoundational (C-)50/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer58 EndpointsREST

For Agents

Generate persuasion copy for a client, report conversion outcomes against specific outputs, rank and diagnose copy, and run multi-stage campaign workflows. Authenticated with a bearer API key carrying read, write, and execute scopes.

Use for: Generate persuasion copy for a client with a specific bot, Report that an output converted so the model learns from it, Rank several candidate outputs and pick the best one, Find which persuasion techniques an output relied on

Not supported: Does not handle email sending, ad buying, or payment processing. Use for generating persuasion copy and tracking its conversion outcomes only.

The Coppica API generates persuasion-engineered marketing copy for a client, then takes real-world outcomes reported against each output so later generations learn from what actually converted. It runs copywriting bots as asynchronous jobs, ranks candidate outputs head-to-head, and diagnoses which persuasion techniques an output used. Around the copy it manages clients, campaigns and their graphs, ideas, offers, avatars, and multi-stage workflows, and builds tracking links so conversion performance can be attributed back to the exact copy that drove it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

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

45%

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.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Coppica API to your agent

Capabilities

Start building with Coppica API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Coppica API

Jentic AI Readiness Score

Coppica 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