canonical: https://jentic.com/apis/polinode.com/polinode

# Polinode API

Polinode API enables programmatic creation, retrieval, update and deletion of networks and employee data. Includes network and node metrics for Enterprise users. Supports surveys and custom fields. The API exposes 33 endpoints secured with basic authentication.

## For AI agents

Programmatically create network, list networks. Covers 33 operations with basic authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create Network
- List Networks
- Get Network
- Update Network
- Delete Network
- Compute Network Modularity

## Use cases

### CRM Operations

Use the Polinode API to perform crm operations programmatically. The API provides 33 endpoints covering core functionality including create network, list networks, get network.

Example prompt: Call POST /networks to create network

### Automated Custom Fields Management

Automate custom fields operations by combining multiple Polinode API endpoints. Agents can list networks and then get network in a single workflow.

Example prompt: Call GET /networks to list networks, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Polinode API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'create network', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/networks` | Create Network |
| GET | `/networks` | List Networks |
| GET | `/networks/{id}` | Get Network |
| PUT | `/networks/{id}` | Update Network |
| DELETE | `/networks/{id}` | Delete Network |
| POST | `/metrics/network/modularity` | Compute Network Modularity |
| POST | `/metrics/network/diameter` | Compute Network Diameter |
| POST | `/metrics/network/avgShortestPathLength` | Compute Average Shortest Path Length |

## Key resources

- **Custom Fields** — Operations for custom fields
- **Employees** — Operations for employees
- **Metrics** — Operations for metrics
- **Networks** — Operations for networks
- **Surveys** — Operations for surveys

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 40 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 76 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/polinode.com/polinode/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Polinode API by hand means setting up HTTP basic auth against app.polinode.com/api/v2, then threading network ids through its paths and posting metric jobs yourself. Through Jentic you install once, import the Polinode API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Polinode puts the network id in the URL path (`/networks/{id}`), so a rule can pin your agent to one network: it can read and update that network and nothing else. You choose the operations it may call, so destructive ones like network deletion are not included unless you add them.
- **Credential handling:** Your Polinode basic-auth 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a network' or 'compute network modularity', and Jentic returns the matching Polinode operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Polinode API use?

The Polinode API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create network with the Polinode API?

Yes. Use the POST /networks endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Polinode API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create network through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create network'. Jentic returns the matching Polinode API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Polinode API have?

The Polinode API exposes 33 endpoints covering custom fields, employees, metrics operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Polinode operations and credentials the agent may use. Since the network id sits in the URL path (`/networks/{id}`), you can pin the agent to a single network so it only reads and updates that one and nothing else. You also choose the exact operations it may call, so destructive ones like Delete Network stay off the list unless you explicitly grant them.