> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raptorcomply.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Raptor Comply gives customers a REST API to maintain NERC internal controls and workflows for syncing cyber assets with a CMDB, work orders with a CMMS, and evidence for a file system.

> Raptor Comply gives customers a REST API to maintain NERC internal controls and workflows for syncing cyber assets with a CMDB, work orders with a CMMS, and evidence for a file system.

[Raptor Comply](https://raptorcomply.com) is a NERC OT compliance platform covering CIP and O\&P standards for generation and transmission owners and operators. The Raptor Comply REST API gives you - compliance leads, OT engineers, and integration developers - programmatic access to your compliance data. Use it to sync assets into your CMDB, feed your SIEM, integrate with your CMMS, or automate any part of your compliance workflow that lives outside the Raptor Comply UI.

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    Set up your API key, understand error responses, and learn key rotation best practices.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first API call in under five minutes using curl, Node.js, or Python.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/overview">
    Explore full request and response schemas, with a live try-it-now playground.
  </Card>

  <Card title="Guides" icon="arrows-rotate" href="/guides/sync-cmdb">
    Step-by-step integration guides, including how to keep your CMDB in sync with Raptor Comply cyber assets.
  </Card>
</CardGroup>

## What the API covers

The current API surface focuses on your core NERC CIP inventory objects. Read access lets you pull the structural data you've already classified in Raptor Comply. Full CRUD on cyber assets means you can drive asset lifecycle changes - additions, retirements, reclassifications - directly from your integration tooling. We are extending the API surface to other objects within the data model: controls, tasks, incidents, access requests, documents and evidence.

| Resource            | Access                       |
| ------------------- | ---------------------------- |
| **Facilities**      | Read                         |
| **Control Centers** | Read                         |
| **Cyber Systems**   | Read                         |
| **Cyber Assets**    | Read, Create, Update, Delete |

All requests go to the base URL `https://api.raptormaps.com` and require the `X-API-Key` header on every call. Each API key is bound to a single organization, so the key alone identifies your tenant. See [Authentication](/authentication) for details.

## Who this is for

**Compliance leads** who need to export or cross-reference CIP inventory data without manual downloads.

**OT engineers** who manage cyber asset lifecycles and want changes reflected in downstream CMDBs or CMMSs without double entry.

**Integration developers** building the pipelines between Raptor Comply and the rest of your operations stack - SIEMs, ticketing systems, asset management platforms, and internal tooling.

If you're a vendor working with Raptor Comply on behalf of a utility, you'll need API credentials scoped to that utility's organization. Ask your Raptor Comply organization admin to generate them.