Install Jentic One Beta

Connect the MyWorkerAI API to your agent

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

List active outbound campaigns the authenticated user owns

Retrieve all leads associated with a specific campaign

Look up an individual lead record by ID for enrichment or follow-up

Classify and filter inbound email content using the AI filter endpoint

Authenticate via JWT bearer token or API key in the Authorization header

GET STARTED

Start building with MyWorkerAI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MyWorkerAI API for, with concrete tasks.

★ Outbound Campaign Lead Sync

Pull lead records from MyWorkerAI campaigns into a CRM, data warehouse, or downstream sequencing tool. Sales operations teams use the GET /api/campaign and /api/campaign/{id}/lead endpoints to mirror campaign progress nightly, so reps see fresh prospect data without logging into MyWorkerAI directly. Saves analytics teams from building screen-scrapers when MyWorkerAI is one input among many in a multi-vendor sales stack.

Fetch every lead from campaign ID 17 via GET /api/campaign/{id}/lead and post each as a contact in HubSpot CRM.

Inbound Email Filtering

Classify inbound email replies to outbound campaigns so reps only see genuine sales conversations rather than auto-responses, out-of-office bounces, and spam. POST /api/email/filter accepts the message body and returns a classification useful for routing replies into a CRM, archive, or human review queue. Cuts manual triage time on high-volume reply queues.

Send the body of an inbound email to POST /api/email/filter and route the reply to the SDR queue if it returns a positive sales-intent classification.

Lead Detail Enrichment

Look up individual lead records by ID to enrich contact data, draft personalised follow-ups, or check campaign attribution. GET /api/campaign/lead/{id} returns the full lead object so an AI agent or rep workflow can compose a tailored outreach without re-querying the campaign list. Common pattern when MyWorkerAI is feeding a personalisation layer or AI-generated reply tool.

Retrieve lead ID 482 with GET /api/campaign/lead/{id} and draft a personalised follow-up email referencing their campaign source.

AI Agent Sales Co-Pilot

Wire MyWorkerAI into an AI sales agent through Jentic so the agent can answer questions like 'how many leads are in my Q3 campaign?' or 'classify this reply' without the developer hand-coding requests. Through Jentic's intent search and execution layer, the four MyWorkerAI operations are reachable in under an hour, with credentials isolated server-side.

Search Jentic for 'list MyWorkerAI campaigns', execute the call, then chain into 'get leads for campaign' to summarise pipeline coverage.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api/campaign

List all campaigns owned by the authenticated user

GET

/api/campaign/{id}/lead

List all leads attached to a specific campaign

GET

/api/campaign/lead/{id}

Retrieve an individual lead record by ID

POST

/api/email/filter

Classify an inbound email body for sales triage

GET

/api/campaign

List all campaigns owned by the authenticated user

GET

/api/campaign/{id}/lead

List all leads attached to a specific campaign

GET

/api/campaign/lead/{id}

Retrieve an individual lead record by ID

POST

/api/email/filter

Classify an inbound email body for sales triage

Why Jentic?

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

Setup

Wiring MyWorkerAI by hand means holding both its bearer token and API key, setting the Authorization header on every call against its Azure host, and mapping the campaign and email-filter calls yourself. Through Jentic you install once, import MyWorkerAI from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

MyWorkerAI puts the campaign id in the URL path (/api/campaign/{id}/lead), so a rule can pin your agent to one campaign. You choose the operations it may call, so you can allow listing campaign leads while leaving the inbound email filter out unless you add it.

Credential isolation

Your MyWorkerAI bearer token and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list outbound campaigns' or 'filter an inbound email', and Jentic returns the matching MyWorkerAI operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MyWorkerAI API through Jentic.

Why is there no official OpenAPI spec for MyWorkerAI API?

MyWorkerAI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyWorkerAI API 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 MyWorkerAI API use?

The MyWorkerAI API supports two schemes: a JWT bearer token and an API key passed in the Authorization header. Both are configured in components.securitySchemes as jwtAuth and apiKeyAuth. Through Jentic, the credential is held in the encrypted vault and injected at execution time, so the raw token never reaches the agent's context.

Can I retrieve all leads in a campaign with the MyWorkerAI API?

Yes. Call GET /api/campaign/{id}/lead with the campaign ID to get the lead list. Use GET /api/campaign first to discover the IDs of campaigns the authenticated user owns, then iterate over them if you need a full pull.

How does the MyWorkerAI email filter endpoint work?

POST /api/email/filter accepts an email body in the request payload and returns a classification used to triage inbound replies to outbound campaigns. The endpoint is most useful for routing replies into SDR queues versus auto-archive paths.

What rate limits apply to the MyWorkerAI API?

Rate limits are not declared in the OpenAPI spec. Treat the service as moderately rate-limited, implement exponential backoff on HTTP 429, and contact MyWorkerAI support for committed throughput on the email filter endpoint if you process high reply volumes.

How do I call the MyWorkerAI API from an AI agent through Jentic?

Install the Jentic SDK with pip install jentic. Use SearchRequest with a query like 'list MyWorkerAI campaigns' to discover the right operation, LoadRequest to load its schema, and ExecutionRequest to call it. Get an agent API key through Jentic One, the self-hosted execution layer.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the four MyWorkerAI operations the agent may call and which credentials it may use. You can allow it to list campaigns and pull campaign leads (GET /api/campaign and GET /api/campaign/{id}/lead) while leaving the inbound email filter (POST /api/email/filter) off unless you add it. Since MyWorkerAI puts the campaign ID in the URL path, a rule can also pin the agent to a single campaign rather than all of them.

MyWorkerAI API

Name: MyWorkerAI API
Brand: MyWorkerAI API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingMarketing Automationbearer, apiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List marketing campaigns, retrieve their leads, and filter inbound emails for sales follow-up using AI classification. Best for B2B sales teams running automated outbound campaigns.

Use for: I need to pull every lead from my Q2 outbound campaign, List all active marketing campaigns in my MyWorkerAI account, Retrieve the details of lead ID 1842 to draft a follow-up email, Filter this incoming email body to decide whether it is a sales reply

Not supported: Does not handle SMS outreach, calendar booking, or contract signing - use for outbound campaign lead sync and AI inbound email filtering only.

Jentic publishes the only available OpenAPI specification for MyWorkerAI API, keeping it validated and agent-ready. MyWorkerAI is an AI-powered marketing automation service that lets teams run outbound campaigns, manage leads, and filter inbound email at scale. The four-endpoint API exposes campaign listing, lead retrieval per campaign, individual lead lookup, and an email filtering operation that classifies messages for sales and marketing follow-up. Authentication supports both JWT bearer tokens and an API key in the Authorization header.

Jentic One on Github View OpenAPI Document