Install Jentic One Beta

Connect the Peerdom API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Peerdom 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.peerdom.app%2Fpeerdom" | 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%2Fapi.peerdom.app%2Fpeerdom" | 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 Peerdom API.

Create, update, and remove peers in the organization

Create, update, and remove roles and their details

Assign peers to roles and manage the holders of a role

Manage groups of roles and peers

List organization maps and projects

GET STARTED

Start building with Peerdom API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Peerdom API for, with concrete tasks.

★ Org Structure Sync Agent

An AI agent keeps Peerdom aligned with an HR system by adding peers when people join, updating roles as responsibilities change, and removing entries when people leave. Through Jentic the agent discovers the peer and role operations by intent and calls them directly, so the org map stays current without manual editing.

Add a new peer and assign them to the role they will hold

Role Assignment Management

Manage which peers hold which roles by creating roles, assigning holders, and removing assignments that no longer apply. This lets an agent reflect a reorganization in Peerdom without a person editing each role by hand.

Assign a peer to an existing role and confirm the role's current holders

Organization Directory Lookup

Read the organization's peers, roles, groups, and maps to answer questions about who does what. The agent can resolve a person's roles or list the members of a group, giving downstream tools an accurate view of the org.

List the roles a given peer holds and the groups they belong to

Key Endpoints

24 endpoints — the peerdom api manages an organization's peers, roles, and groups, along with the maps that show how they connect.

METHOD

PATH

DESCRIPTION

GET

/peers

List peers

POST

/peers

Create a peer

GET

/roles

List roles

POST

/roles

Create a role

POST

/roles/{roleId}/peers

Assign a peer to a role

GET

/peers

List peers

POST

/peers

Create a peer

GET

/roles

List roles

POST

/roles

Create a role

POST

/roles/{roleId}/peers

Assign a peer to a role

Why Jentic?

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

Setup

Wiring the Peerdom API by hand means handling its X-Api-Key auth and the create-peer then assign-role sequence yourself. Through Jentic you install once, import Peerdom from the API Directory, store the key once, and your agent calls it.

Permission scoping

Peerdom identifies peers, roles, and groups by an id in the request path, so a rule bounds which operations your agent may call. You choose those operations, so destructive ones like deleting a peer or role are not included unless you add them.

Credential isolation

Your Peerdom 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.

Intent-based discovery

Agents search Jentic by intent such as 'add a peer' or 'assign a peer to a role', and Jentic returns the matching Peerdom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Peerdom API through Jentic.

What authentication does the Peerdom API use?

The Peerdom API authenticates with an API key sent in the X-Api-Key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I add a peer with the Peerdom API?

Yes. Call POST /peers to create the peer, then use POST /roles/{roleId}/peers to assign them to a role. GET /peers lists the current peers so you can confirm the addition.

What are the rate limits for the Peerdom API?

The OpenAPI spec does not specify rate limits. Check the Peerdom documentation at https://api.peerdom.app/v1/docs before running bulk sync jobs.

Is there a Peerdom MCP server?

You don't need an MCP server to give your agent the Peerdom API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the peer and role operations it needs.

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

Yes. Write a rule that allows only the peer and role read and create operations, so the agent can build structure but cannot delete a peer or role, and every call it makes is logged.

How do I add a peer with the Peerdom API through Jentic?

Search Jentic for 'add a peer to the organization', and it returns the POST /peers and role-assignment operations with their input schemas so your agent updates the org directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Peerdom App Peerdom API

Name: Peerdom API
Brand: Peerdom API
Availability: InStock

Official vendor OpenAPI document · agent-readyHR recruitingEmployee ManagementapiKey24 EndpointsREST

For Agents

Create, update, and remove peers, roles, and groups in an organization, and assign peers to the roles they hold. Read organization maps, projects, and tenant details.

Use for: Add a new peer to the organization, Create a role and assign a peer to it, Update a peer's details, List the roles a peer holds

Not supported: Does not handle payroll, time tracking, or applicant tracking. Use for managing organization peers, roles, and structure only.

The Peerdom API manages an organization's peers, roles, and groups, along with the maps that show how they connect. It creates, updates, and removes peers and roles, assigns peers to the roles they hold, and reads projects and tenant details, so an agent can keep an org's structure current.

Jentic One on Github View OpenAPI Document

Connect the Peerdom API to your agent

Capabilities

Start building with Peerdom API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Peerdom App Peerdom API