Peoplefinderspro Self Service Developer API
Browse all Peoplefinderspro APIsOfficial vendor OpenAPI document · agent-readyAI/MLMl Inferencenone5 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.
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.
1
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%2Fpeoplefinderspro.com%2Fpeoplefinderspro" | sh2
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%2Fpeoplefinderspro.com%2Fpeoplefinderspro" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Patterns agents use Self Service Developer API for, with concrete tasks.
★ peoplefinderspro.com Integration
Integrate Self Service Developer API into your application or workflow to automate operations and access resources programmatically.
Use the Self Service Developer API to perform operations against peoplefinderspro.com resources.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PeopleFinders Pro Self Service Developer API by hand means assembling its contact, email, phone, and identity enrichment request payloads against api.peoplefinderspro.com yourself. Through Jentic you install once, import the Self Service Developer API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
This API takes its lookup criteria in the request body across enrichment operations like /contact/enrich, /email/enrich, and /phone/enrich, so scoping is operations-only: limit the agent to the operations it needs, such as email enrichment, and leave identity verification out of the allowed set unless you add it.
Credential isolation
Your PeopleFinders Pro credential 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 'enrich a contact from an email address', and Jentic returns the matching Self Service Developer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Self Service Developer API through Jentic.
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.
Can I limit what my agent is allowed to do with the Self Service Developer API?
Yes. Because you run Jentic One yourself, your own rules decide which of this API's enrichment operations the agent may call and which credential it uses. Scoping here is operations-only: since each lookup takes its criteria in the request body, you can allow just the operations you need, such as /email/enrich, and leave others like /contact/enrich, /phone/enrich, or identity verification out of the allowed set. The agent can only invoke the operations you have permitted.
GET STARTED