Install Jentic One Beta

Connect the Cometly API to your agent

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

Send a single attribution event via POST /events with contact and conversion data

Stream high-volume events via POST /events/batch for server-side tracking pipelines

Create, list, fetch, update, and delete contact records under /contacts

Trigger a data export via POST /exports for warehouse loading

Poll export status and retrieve the download URL via GET /exports/{exportId}

GET STARTED

Start building with Cometly API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cometly API for, with concrete tasks.

★ Server-Side Conversion Tracking

Send purchase, signup, or lead events from a backend service to POST /events so attribution survives ad blockers and Safari ITP. Each event carries the contact reference plus conversion value, letting Cometly tie revenue back to the original ad click. Reliable for Shopify checkouts, Stripe webhooks, and CRM-triggered events.

POST a purchase event to /events with contactId, value 49.99, currency USD, and event_name 'purchase'

Bulk Backfill of Historical Conversions

When onboarding to Cometly, replay months of historical orders through POST /events/batch so the attribution engine can rebuild lookback windows. Batch ingestion accepts arrays of events in a single request, reducing rate-limit pressure compared with one-by-one POSTs.

POST a batch of 500 historical purchase events to /events/batch and return the count accepted

Warehouse Export Pipeline

Trigger POST /exports to dump attribution data into the warehouse on a schedule, then poll GET /exports/{exportId} until the status is ready and download the resulting file. This gives BI tools and downstream MMM models a clean source of truth that combines Cometly's attribution with internal revenue data.

Create an export with date_range last_30_days, poll until status is complete, and return the download URL

AI Agent Attribution Reporter via Jentic

An AI agent connected to Jentic can answer 'how much revenue did Meta drive last week?' by triggering a Cometly export, polling for completion, and summarising the results - all without raw API key exposure. Jentic stores the bearer token in your Jentic One instance and returns only execution results to the agent.

Use Jentic to search 'send a conversion event to cometly', load the operation, and execute with a sample purchase event

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for cometly api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/events

Send a single attribution event

POST

/events/batch

Send a batch of events

POST

/contacts

Create a contact

GET

/contacts

List contacts

PUT

/contacts/{contactId}

Update a contact

POST

/exports

Create a data export

GET

/exports/{exportId}

Get export status and download URL

POST

/events

Send a single attribution event

POST

/events/batch

Send a batch of events

POST

/contacts

Create a contact

GET

/contacts

List contacts

PUT

/contacts/{contactId}

Update a contact

POST

/exports

Create a data export

GET

/exports/{exportId}

Get export status and download URL

Why Jentic?

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

Setup

Wiring Cometly by hand means learning its bearer auth, building server-side conversion event calls, and managing your own retries and batching. Through Jentic you install once, import Cometly from the API Directory, store the token once, and your agent calls it.

Permission scoping

Cometly puts the contact and export ids in the URL path (/contacts/{contactId}, /exports/{exportId}), so a rule can pin your agent to reading and updating a specific contact or export. You choose the operations it may call, so you can allow conversion event tracking while leaving contact updates out unless you add them.

Credential isolation

Your Cometly bearer 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 'send a conversion event to Cometly' or 'export attribution data', and Jentic returns the matching Cometly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cometly API through Jentic.

Why is there no official OpenAPI spec for Cometly API?

Cometly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cometly via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Cometly API use?

Cometly uses a bearer token in the Authorization header. Through Jentic the key is stored encrypted in your Jentic One instance and never enters the agent context - the agent only receives the response of the operation it called.

Can I send conversion events from the server side with the Cometly API?

Yes. POST /events accepts a single conversion event and POST /events/batch accepts an array of events for bulk ingestion. Both expect a contact reference and the conversion attributes (event_name, value, currency).

What are the rate limits for the Cometly API?

Cometly does not document a hard public rate limit; in practice, single-event POSTs above a few hundred per minute should move to /events/batch. Expect 429 responses at extreme volume and back off.

How do I send a conversion event through Jentic?

Search Jentic for 'send a conversion event to cometly', load the schema for POST /events, and execute with the contact reference and event details. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).

Can I export Cometly attribution data to a warehouse?

Yes. POST /exports creates a data export job, GET /exports lists exports, and GET /exports/{exportId} returns the status plus a download URL once the export is complete. Schedule this from a warehouse loader to refresh attribution data nightly.

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

Yes. Because you run Jentic One yourself, your own rules decide which Cometly operations the agent may call, so you can allow it to send conversion events with POST /events and POST /events/batch while leaving contact updates and deletes out unless you add them. Cometly puts the contact and export ids in the URL path (/contacts/{contactId}, /exports/{exportId}), so a rule can pin the agent to a specific contact or export rather than the whole account. Your bearer token stays with your Jentic One instance and is injected only for the operations you permit.

Cometly API

Name: Cometly API
Brand: Cometly API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAnalyticsProduct Analyticsbearer10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send server-side conversion events, manage contact records, and export attribution data from Cometly with one bearer token.

Use for: I need to send a server-side purchase event to Cometly, Create a Cometly contact record from a new signup, Update the email address on an existing Cometly contact, Batch upload yesterday's conversions to Cometly

Not supported: Does not handle ad creative management, audience targeting, or campaign budgeting - use for server-side conversion tracking and attribution data export only.

Jentic publishes the only available OpenAPI specification for Cometly API, keeping it validated and agent-ready. Cometly is an ad attribution and tracking platform; its API exposes contact records, event ingestion, and data exports so server-side code can stream conversions, identify users, and pull historical data for offline analysis. Use it to attribute marketing spend to outcomes, send server-side conversion events that survive ad blockers, and export attribution data into a warehouse.

Jentic One on Github View OpenAPI Document

Connect the Cometly API to your agent

Capabilities

Start building with Cometly API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cometly API