Install Jentic One Beta

Connect the PDQ Connect to your agent

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

List software deployments and track their status across managed devices

Inventory managed devices with hardware and software details

Retrieve detailed information for individual devices by ID

Organize devices into logical groups for targeted management

Browse and inspect software packages available for deployment

GET STARTED

Start building with PDQ Connect API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PDQ Connect API for, with concrete tasks.

★ Fleet Software Deployment Monitoring

Monitor the status of software deployments across managed devices. The API provides a list of all deployments with their current state, enabling IT teams to identify failed installations, track rollout progress, and verify that critical patches reached all target devices.

GET /v1/api/deployments to list all deployments and filter for those with failed status to identify devices needing attention

Device Inventory and Compliance Auditing

Query the complete inventory of managed devices for compliance reporting, asset management, or security audits. Retrieve device details including hardware specifications, installed software, and group membership to verify that endpoints meet organizational standards.

GET /v1/api/devices to list all managed devices, then GET /v1/api/devices/{device_id} for specific devices requiring detailed compliance checks

Group-Based Device Management

Organize devices into groups for targeted software deployments, policy application, or reporting. Device groups enable IT administrators to segment their fleet by department, location, role, or any custom criteria, then apply management actions to specific segments.

GET /v1/api/groups to list all device groups and identify the correct target group for a targeted deployment action

AI Agent IT Operations via Jentic

AI agents perform IT management tasks by calling PDQ Connect through Jentic. The agent searches for device management operations, loads endpoint schemas, and executes inventory queries or deployment checks without managing bearer tokens or understanding the PDQ Connect API structure directly.

Search Jentic for 'list managed devices', load the /v1/api/devices schema, and execute to retrieve the current device inventory

Key Endpoints

6 endpoints — pdq connect api provides programmatic access to it device management operations including deploying software packages, inventorying managed devices, and organizing devices into groups.

METHOD

PATH

DESCRIPTION

GET

/v1/api/deployments

List all software deployments

GET

/v1/api/devices

List all managed devices

GET

/v1/api/devices/{device_id}

Retrieve details for a specific device

GET

/v1/api/groups

List all device groups

GET

/v1/api/packages

List all available software packages

GET

/v1/api/packages/{package_id}

Retrieve details for a specific package

GET

/v1/api/deployments

List all software deployments

GET

/v1/api/devices

List all managed devices

GET

/v1/api/devices/{device_id}

Retrieve details for a specific device

GET

/v1/api/groups

List all device groups

GET

/v1/api/packages

List all available software packages

GET

/v1/api/packages/{package_id}

Retrieve details for a specific package

Why Jentic?

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

Setup

Wiring PDQ Connect by hand means setting up its bearer auth against app.pdq.com and paging through devices, deployments, groups, and packages yourself. Through Jentic you install once, import PDQ Connect from the API Directory, store the token once, and your agent calls it.

Permission scoping

PDQ Connect puts the resource id in the URL path (/v1/api/devices/{device_id}, /v1/api/packages/{package_id}), so a rule can pin your agent to reading a specific device or package. The endpoints here are read-only inventory queries, and you choose which operations the agent may call so only those run.

Credential isolation

Your PDQ Connect bearer token from the admin console 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 managed devices' or 'check software deployment status', and Jentic returns the matching PDQ Connect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PDQ Connect API through Jentic.

What authentication does the PDQ Connect API use?

PDQ Connect API uses bearer token authentication. You generate an API key from your PDQ Connect admin console and pass it as a Bearer token in the Authorization header. Through Jentic, this token is stored encrypted in the vault and injected automatically.

Can I list all managed devices in my organization?

Yes. GET /v1/api/devices returns all managed devices in your PDQ Connect organization. For individual device details including hardware specs and installed software, use GET /v1/api/devices/{device_id} with the specific device identifier.

How do I check deployment status across my fleet?

GET /v1/api/deployments returns all software deployments with their current status. You can identify failed, pending, or completed deployments to track rollout progress across your managed endpoints.

What are device groups used for in PDQ Connect?

Device groups organize managed endpoints into logical collections for targeted actions. GET /v1/api/groups lists all configured groups. Groups enable segmented software deployment, policy application, and filtered reporting by department, location, or custom criteria.

How do I manage devices through Jentic with PDQ Connect?

Install with pip install jentic, search for 'list managed devices' or 'check deployment status'. Jentic returns the /v1/api/devices or /v1/api/deployments operation schemas. Execute to query your fleet. Jentic handles bearer token injection automatically.

Is the PDQ Connect API in stable release?

The current API version is 0.01-beta, indicating it is in beta status. While functional, endpoints and response schemas may change. Check the PDQ Connect documentation for migration guidance when stable versions are released.

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

Yes. Because you run Jentic One yourself, your own rules decide which PDQ Connect operations and credentials the agent may use, and you can allow only a subset such as GET /v1/api/devices or GET /v1/api/deployments. Since PDQ Connect puts the resource id in the URL path (GET /v1/api/devices/{device_id}, GET /v1/api/packages/{package_id}), a rule can pin the agent to reading one specific device or package. The endpoints here are read-only inventory queries, so the agent can look up devices, deployments, groups, and packages but cannot change your fleet.

PDQ Connect

Name: PDQ Connect API
Brand: PDQ Connect
Availability: InStock

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer6 EndpointsREST

For Agents

Deploy software packages, inventory devices, and manage device groups across IT fleets. Programmatic access to PDQ Connect device management operations.

Use for: I need to list all managed devices in my fleet, I want to check the status of a software deployment, Get details for a specific device by its ID, List all device groups for targeted deployments

Not supported: Does not handle remote desktop access, patch creation, or network monitoring - use for device inventory, software deployment tracking, and group management only.

PDQ Connect API provides programmatic access to IT device management operations including deploying software packages, inventorying managed devices, and organizing devices into groups. The API enables IT administrators to list deployments, query device details, manage device groups, and access package information across their fleet. It is designed for organizations managing Windows endpoints at scale.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

10%

Example Density

How richly the API is illustrated with examples.

80%

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

43%

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.

50%

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

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PDQ Connect to your agent

Capabilities

Start building with PDQ Connect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PDQ Connect

Jentic AI Readiness Score

Connect

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