canonical: https://jentic.com/apis/swarmnode.ai/swarmnode

# SwarmNode API

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.

## For AI agents

Programmatically create an agent, list all agents. Covers 22 operations with bearer authentication.

## Scope

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

## Capabilities

- Create an agent
- List all agents
- Retrieve an agent
- Update an agent
- Delete an agent

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/agents` | Create an agent |
| GET | `/v1/agents` | List all agents |
| GET | `/v1/agents/{id}` | Retrieve an agent |
| PATCH | `/v1/agents/{id}/update` | Update an agent |
| DELETE | `/v1/agents/{id}/delete` | Delete an agent |
| POST | `/v1/stores` | Create a store |
| GET | `/v1/stores` | List all stores |
| GET | `/v1/stores/{id}` | Retrieve a store |

## Key resources

- **Agents** — Operations related to Agents
- **Builds** — Operations related to Builds
- **Cron Jobs** — Operations related to Cron Jobs
- **Executions** — Operations related to Executions
- **Executor Jobs** — Operations related to Executor Jobs

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/swarmnode.ai/swarmnode/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SwarmNode API operations and credentials the agent may use. Because each resource id sits in the URL path, such as `/v1/agents/{id}` and `/v1/stores/{id}`, you can pin the agent to a single agent or store and let it read and update only that resource. Destructive operations like deleting an agent or a store are excluded unless you explicitly add them to the agent's allowed set.