canonical: https://jentic.com/apis/digitalpilot.app/digitalpilot

# Digitalpilot App DigitalPilot API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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
- Register webhooks for lead and visitor events and send a test delivery

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Leads** — List and update leads and move them through configured lead stages
- **Reports** — Retrieve channel, UTM, dashboard, overview, and target-account visit reports for a tag
- **Target accounts** — Create and manage target accounts and target-account lists for account-based marketing
- **Contacts** — Validate emails, reveal a contact email, and search contacts by company domain
- **Webhooks** — Create, update, list, and test webhooks for lead and visitor events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 55 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 83 / 100
  - AI-Readiness & Agent Experience: 32 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/digitalpilot.app/digitalpilot/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **6sense** — 6sense is an account-based intent and ABM platform, while DigitalPilot focuses on website visitor identification and lead tracking.
- **Clearbit** — Clearbit enriches companies and contacts, complementing DigitalPilot's visitor and lead data.
- **Apollo** — Apollo provides sales prospecting and contact data to act on leads DigitalPilot captures.
- **Plausible Analytics** — Plausible is privacy-focused web analytics, while DigitalPilot ties visits to identified companies and leads.

## FAQ

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