Path Selection

Pick Your Integration Path

Start with the path that matches your deployment model today, then expand without replatforming. Both routes run on the same security perimeter, key model, and tenant policy controls.

Path A · System Sync

REST API

Best for platform integrations, command dashboards, and managed data exchange.

  • Patrol and incident read flows for operational awareness
  • Guards, sites, clients with soft-delete lifecycle controls
  • Standard request IDs and rate-limit headers for predictable retries
Open API Reference Download OpenAPI
Path B · Agent Workflow

MCP Gateway

Best for AI copilots and autonomous workflows that need governed tool execution.

  • JSON-RPC methods for initialize, tools/list, and tools/call
  • Shared API key auth and scope enforcement across both surfaces
  • Consistent tenant boundaries for external copilots and partner agents
View MCP Endpoint

Implementation Journey

5-Step Go-Live Sequence

Follow this left-to-right sequence to move from key setup to production automation.

1

Provision Key

Create a scoped API key in your Patrol6 tenant integrations settings.

2

Validate Auth

Call `GET /guards` to confirm headers, scope, and tenant-bound access.

3

Sync Data

Pull patrols and incidents, then upsert entities into your command workflows.

4

Harden Runtime

Implement deterministic retry using `Retry-After` and rate-limit headers.

5

Activate MCP

Connect agents to MCP Gateway for secure tool-based orchestration.

Permissions

Resource Permission Matrix

Model scopes at key creation to enforce least-privilege integrations from day one.

Resource Default Access Write Behavior Relevant Scopes
Patrols Read Only Not writable in V1 `PATROLS_READ`
Incidents Read Only Not writable in V1 `INCIDENTS_READ`
Guards CRUD Delete is soft-delete `GUARDS_READ`, `GUARDS_WRITE`
Sites CRUD Delete is soft-delete `SITES_READ`, `SITES_WRITE`
Clients CRUD Delete is soft-delete `CLIENTS_READ`, `CLIENTS_WRITE`
MCP Tools Policy Matched Follows same REST scope checks Inherited from key scopes

Error Recovery

Operational Failure Handling

Use explicit remediation behavior to keep integrations stable under load and policy errors.

401 Invalid Or Missing Key

Check `Authorization: Bearer <key>` or `x-api-key`, then verify key activation status.

403 Scope Denied

Regenerate key with the required scope for the operation you are performing.

429 Rate Limit Exceeded

Honor `Retry-After` and `RateLimit-Reset` before retrying with backoff.

System Map

Patrol6 Integration Control Map

Patrol360, Command Center, and PatrolAI are exposed externally through Secure Edge with consistent policy and identity controls across REST and MCP.

Patrol360 (P360)
Command Center (CC)
PatrolAI (PAI)
Patrol6 DB
Secure Edge (SE)
REST API
MCP Gateway (MCPG)
Partners + Agents