For Agents
Programmatically create network, list networks. Covers 33 operations with basic authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Polinode 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%2Fpolinode.com%2Fpolinode" | shStep 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%2Fpolinode.com%2Fpolinode" | 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.
What an agent can do with Polinode API.
Create Network
List Networks
Get Network
Update Network
GET STARTED
Use for: I need to network, I want to networks, Search for network, Find all network
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
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.
Delete Network
Compute Network Modularity
Patterns agents use Polinode API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'create network', load the operation schema, and execute with Jentic-managed credentials
33 endpoints — polinode api enables programmatic creation, retrieval, update and deletion of networks and employee data.
METHOD
PATH
DESCRIPTION
/networks
Create Network
/networks
List Networks
/networks/{id}
Get Network
/networks/{id}
Update Network
/networks/{id}
Delete Network
/metrics/network/modularity
Compute Network Modularity
/metrics/network/diameter
Compute Network Diameter
/metrics/network/avgShortestPathLength
Compute Average Shortest Path Length
/networks
Create Network
/networks
List Networks
/networks/{id}
Get Network
/networks/{id}
Update Network
/networks/{id}
Delete Network
/metrics/network/modularity
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Polinode API through Jentic.
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.
Compute Network Modularity
/metrics/network/diameter
Compute Network Diameter
/metrics/network/avgShortestPathLength
Compute Average Shortest Path Length