canonical: https://jentic.com/apis/api.peerdom.app/peerdom # Peerdom App Peerdom API 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. ## For AI 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. ## Scope Does not handle payroll, time tracking, or applicant tracking. Use for managing organization peers, roles, and structure only. ## Capabilities - 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 - Read tenant details for the organization ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: List the roles a given peer holds and the groups they belong to ## Key endpoints | 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 | ## Key resources - **Peers** — Create, update, remove, and read the people in the organization - **Roles and groups** — Manage roles, their holders, and groups of roles and peers - **Maps and tenant** — Read organization maps, projects, and tenant details ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **ChartHop** — Org chart and people platform compared with Peerdom's peer-and-role model - **BambooHR** — HR system of record that pairs with Peerdom's org structure - **Personio** — HR platform that feeds people data into Peerdom ## FAQ ### 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.