What authentication does the Self Service Developer API use?

The Self Service Developer API uses none authentication. Through Jentic, credentials are stored encrypted and injected at execution time so they never enter the agent's context.

How many endpoints does the Self Service Developer API have?

The Self Service Developer API exposes 5 endpoints across its surface area.

Peoplefinderspro Self Service Developer API

Name: Self Service Developer API
Brand: Self Service Developer API
Availability: InStock

Browse all Peoplefinderspro APIs

✓ Official Vendor SpecData IntelligencePeople Searchnone5 EndpointsREST

For Agents

Manage peoplefinderspro.com resources and operations programmatically.

Use for: I need to integrate with peoplefinderspro.com, How do I access peoplefinderspro.com data programmatically, Help me automate peoplefinderspro.com tasks

Not supported: Provides access to peoplefinderspro.com resources and operations as documented in the OpenAPI specification.

Self Service Developer API documentation and demo. ##Getting Started You will need an API access profile user and password in order to access search endpoints. Your access profile user and password is used for authenticating all requests to our search API. You MUST pass the user and password each time you perform a search request.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Self Service Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Self Service Developer 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://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 Self Service Developer API.

Access and manage peoplefinderspro.com resources

Integrate peoplefinderspro.com functionality into workflows

Automate peoplefinderspro.com operations

Use Cases

GET STARTED

Start building with Self Service Developer API

Explore with Jentic

View OpenAPI Document

Why Jentic?

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

Credential isolation

peoplefinderspro.com credentials are stored encrypted in the Jentic vault and injected at execution time. Raw credentials never appear in agent prompts, transcripts, or response payloads.

Intent-based discovery

Agents search by intent and Jentic returns the matching endpoint with its schema and any required parameters.

Time to first call

Direct peoplefinderspro.com integration: days to weeks to model all resources and operations. Through Jentic: under 1 hour — search, load schema, execute.