Install Jentic One Beta

Connect the DigitalPilot API to your agent

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

Pull domain-level visitor activity and channel reports for each workspace tag

Capture leads and move them through the lead stages you configure

Build and maintain target-account lists for account-based outreach

Validate a contact email address and reveal a contact email from a domain search

Report on UTM attribution, dashboard, and overview metrics per tag

GET STARTED

Start building with DigitalPilot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DigitalPilot API for, with concrete tasks.

★ Agent-Driven Lead Triage

An AI agent connected through Jentic pulls new leads for a workspace tag, reads each lead's channel and UTM attribution, and moves qualified leads to a later lead stage so sales sees a triaged pipeline. The DigitalPilot API exposes the lead, lead-stage, and report operations the agent needs, and Jentic injects the API key at call time.

List this week's leads for a workspace tag, read each lead's UTM source, and move qualified leads to a later lead stage

Account-Based Marketing Lists

Teams running account-based campaigns maintain target-account lists and watch which accounts visit the site. The DigitalPilot API creates target accounts, organizes them into lists, and reports target-account visits by channel so the team focuses on engaged accounts.

Create a target-account list, add three company accounts to it, and fetch the target-account visit report for the tag

Website Visitor Reporting

Growth teams need to know which companies visit and through which channels. The DigitalPilot API returns domain-level activity plus channel, UTM, dashboard, and overview reports for a workspace tag, giving a per-company view of site engagement.

Fetch the UTM and channel reports for a workspace tag and summarize the top five referring channels

Contact Email Validation

Before adding a prospect to outreach, teams validate the address and recover a contact email from a company domain. The DigitalPilot API validates an email address, reveals a contact email, and searches contacts by domain so lists stay clean.

Validate a prospect's email address and, if invalid, search the company domain for a valid contact email

Key Endpoints

29 endpoints — the digitalpilot api identifies the companies visiting your website and turns that traffic into managed leads.

METHOD

PATH

DESCRIPTION

GET

/v1/tags/{id}/leads

List leads for a workspace tag

PUT

/v1/tags/{id}/leads/{leadId}

Update a lead

GET

/v1/tags/{id}/reports/dashboard

Get the dashboard report

GET

/v1/tags/{id}/reports/utm

Get the UTM report

GET

/v1/tags/{id}/target-accounts

List target accounts

POST

/v1/tags/{id}/target-accounts

Add a target account to the default list

POST

/v1/tags/{id}/contacts/email-validator

Validate an email address

POST

/v1/tags/{id}/webhooks

Create a webhook

GET

/v1/tags/{id}/leads

List leads for a workspace tag

PUT

/v1/tags/{id}/leads/{leadId}

Update a lead

GET

/v1/tags/{id}/reports/dashboard

Get the dashboard report

GET

/v1/tags/{id}/reports/utm

Get the UTM report

GET

/v1/tags/{id}/target-accounts

List target accounts

POST

/v1/tags/{id}/target-accounts

Add a target account to the default list

POST

/v1/tags/{id}/contacts/email-validator

Validate an email address

POST

/v1/tags/{id}/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring DigitalPilot by hand means managing its `x-api-key` header auth and threading your workspace tag id through every /v1/tags/{id} path. Through Jentic you install once, import DigitalPilot from the API Directory, store the key once, and your agent calls it.

Permission scoping

DigitalPilot puts the workspace tag id in the URL path (/v1/tags/{id}/...), so a rule can pin your agent to one tag: it can read that tag's leads and reports and nothing else. You choose which operations it may call, so write operations like deleting a lead stage or a target-account list are not included unless you add them.

Credential isolation

Your DigitalPilot API 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 'list new leads' or 'get the UTM report', and Jentic returns the matching DigitalPilot operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using DigitalPilot API through Jentic.

What authentication does the DigitalPilot API use?

The DigitalPilot API authenticates with an API key sent in the `x-api-key` request header, per its OpenAPI spec. Create the key in your DigitalPilot account and send it on every call. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

Can I track website visitors and manage leads with the DigitalPilot API?

Yes. The API returns domain-level visitor activity along with channel, UTM, dashboard, and overview reports for a workspace tag, and it lets you list and update leads and move them through lead stages you define. You can also build target-account lists and validate contact email addresses.

Is there a DigitalPilot MCP server?

You don't need an MCP server to give your agent the DigitalPilot API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the leads, reports, and target-account operations. Because operations load on demand, your agent's context stays lean instead of holding another server's tool definitions.

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

Yes. Write a rule that allows only the lead-reading and report operations for a single workspace tag, so the agent can pull leads and UTM or dashboard reports for that tag and cannot create webhooks or delete target-account lists. Every call it makes is logged.

What are the rate limits for the DigitalPilot API?

The OpenAPI spec does not specify rate limits. Check the DigitalPilot documentation at https://digitalpilot.app for current limits before running high-volume report or lead jobs.

How do I pull a lead report with the DigitalPilot API through Jentic?

Search Jentic for an intent like 'get the dashboard report', add the DigitalPilot API from the directory, and store your API key once. Your agent then calls the report and lead operations for the workspace tag you choose. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Digitalpilot App DigitalPilot API

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey29 EndpointsREST

For Agents

Identify companies visiting a website, pull channel and UTM reports, manage leads and lead stages, build target-account lists, and validate contact emails for a DigitalPilot workspace tag.

Use for: I need to pull this week's lead list for a workspace tag, Find all target accounts that visited our site, Update a lead's stage after a sales call, Validate an email address before adding it as a contact

Not supported: Does not handle email campaign sending, paid ad buying, or CRM deal forecasting. Use for website visitor identification, lead tracking, and account-based marketing only.

The DigitalPilot API identifies the companies visiting your website and turns that traffic into managed leads. It returns domain-level visitor activity with channel, UTM, dashboard, and overview reports for a workspace tag, captures and updates leads through lead stages you define, and builds target-account lists for account-based marketing. Contact operations validate an email address, reveal a contact email, and search contacts by company domain, while webhooks push new lead and visitor events to your systems.

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

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

67%

Example Density

How richly the API is illustrated with examples.

92%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

66%

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.

60%

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: 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: C+Signals: 1

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DigitalPilot API to your agent

Capabilities

Start building with DigitalPilot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Digitalpilot App DigitalPilot API

Jentic AI Readiness Score

DigitalPilot 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