PDQ Connect

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

✓ Official Vendor SpecCloud InfrastructureComputebearer6 EndpointsREST

For Agents

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

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with PDQ Connect API

Explore with Jentic

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PDQ Connect bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access — the raw API key from your PDQ Connect admin console never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list managed devices' or 'check software deployment status') and Jentic returns matching PDQ Connect operations with full schemas for devices, deployments, groups, and packages.

Time to first call

Direct integration: 1-2 days for auth setup, endpoint discovery, and response parsing. Through Jentic: under 15 minutes — search, load schema, execute.

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.