Skip to main content
2501 is an AIOps platform. You point it at the machines you operate, give it a few rules about how your environment works, and it handles incoming tickets autonomously — investigating, fixing, and reporting back in the ticket your team already lives in.

​
How it fits together

Command Center

Web UI for everything: hosts, agents, rules, knowledge, tasks, and analytics.

Engine

The backend that spawns agents, orchestrates them, and drives tool execution.

Agents

LLM-powered operators bound to a host and a specialty. They run the work.

Gateways

Bridges between your ticketing system (ServiceNow) and the agent fleet.

​
A typical flow

  1. A ticket lands in your ITSM.
  2. The gateway reads it, picks the right host and agent, and creates a job.
  3. The agent runs commands on the target host, observes results, and adapts.
  4. The gateway posts the outcome back to the ticket.
For the full lifecycle, see Agentic Flow.

Quickstart

Install, deploy, and run a first agent in under 15 minutes.

Concepts

Agents, hosts, tasks, jobs, tickets, gateways.

Prompting Guide

How to write tasks, specialties, rules, and gateway prompts that work.

Best Practices

Scoping, knowledge, dynamic context, testing — patterns that scale.

​
Driving 2501 as code

Your hosts and agents are reachable over a versioned HTTP API - the same endpoints Command Center’s own screens are built on. Generate an API key and script against your inventory from a pipeline, a CMDB sync, or a one-off shell script.

API Overview

Authentication, organizations, pagination, and errors.

API Keys

Generate a scoped key, and revoke it when you are done.