For Agents
Programmatically create an agent, list all agents. Covers 22 operations with bearer authentication.
I need to an agent, I want to all agents, Search for an agent, Find all an agent
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SwarmNode 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%2Fswarmnode.ai%2Fswarmnode" | 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%2Fswarmnode.ai%2Fswarmnode" | 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 SwarmNode API.
Create an agent
List all agents
Retrieve an agent
Update an agent
GET STARTED
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
REST API for managing AI agents, stores, builds, executions, and cron jobs on the SwarmNode platform. The API exposes 22 endpoints secured with bearer authentication.
Delete an agent
Patterns agents use SwarmNode API for, with concrete tasks.
★ Developer Tools Operations
Use the SwarmNode API to perform developer tools operations programmatically. The API provides 22 endpoints covering core functionality including create an agent, list all agents, retrieve an agent.
Call POST /v1/agents to create an agent
Automated Agents Management
Automate agents operations by combining multiple SwarmNode API endpoints. Agents can list all agents and then retrieve an agent in a single workflow.
Call GET /v1/agents to list all agents, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SwarmNode 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 bearer tokens manually.
Search Jentic for 'create an agent', load the operation schema, and execute with Jentic-managed credentials
22 endpoints — rest api for managing ai agents, stores, builds, executions, and cron jobs on the swarmnode platform.
METHOD
PATH
DESCRIPTION
/v1/agents
Create an agent
/v1/agents
List all agents
/v1/agents/{id}
Retrieve an agent
/v1/agents/{id}/update
Update an agent
/v1/agents/{id}/delete
Delete an agent
/v1/stores
Create a store
/v1/stores
List all stores
/v1/stores/{id}
Retrieve a store
/v1/agents
Create an agent
/v1/agents
List all agents
/v1/agents/{id}
Retrieve an agent
/v1/agents/{id}/update
Update an agent
/v1/agents/{id}/delete
Delete an agent
/v1/stores
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SwarmNode API by hand means attaching its bearer token to every call against api.swarmnode.ai and managing its agent, store, and execution routes yourself. Through Jentic you install once, import the SwarmNode API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The SwarmNode API puts each resource id in the URL path (/v1/agents/{id}, /v1/stores/{id}), so a rule can pin your agent to one agent or store: it can read and update that resource and nothing else. You choose the operations it may call, so destructive ones like deleting an agent or a store are not included unless you add them.
Credential isolation
Your SwarmNode API bearer token 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 an agent' or 'run an agent executor job', and Jentic returns the matching SwarmNode API 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using SwarmNode API through Jentic.
What authentication does the SwarmNode API use?
The SwarmNode API uses a Bearer token in the Authorization header. 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 an agent with the SwarmNode API?
Yes. Use the POST /v1/agents endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SwarmNode 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 an agent through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an agent'. Jentic returns the matching SwarmNode API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SwarmNode API have?
The SwarmNode API exposes 22 endpoints covering agents, builds, cron jobs operations.
Create a store
/v1/stores
List all stores
/v1/stores/{id}
Retrieve a store