Skip to main content
You want to talk to AcuSight from your own code — script the platform or wire it into an agent. Everything the web app does goes through a documented REST API, plus the Co-Pilot over MCP for AI integrations.

​
Your path

1

Get oriented on the API

Auth, the response envelope, and how routes are organized. See REST API overview.
2

Browse the reference

The full endpoint reference is generated from the platform’s OpenAPI spec — it’s the single source of truth, never hand-written. See API reference.
3

Integrate the Co-Pilot

AcuSight ships the Co-Pilot, an AI assistant exposed over MCP, so you can query the platform from your own agent. See Co-Pilot / MCP integration.

​
Good to know

  • One response envelope everywhere. API responses wrap their payload as { success, data, error, meta } — code against that shape once.
  • Bearer-token auth. Requests carry the bearer token from your session, and calls are automatically scoped to your organization. Devices authenticate with their own device key, not user tokens. See REST API overview.

​
Start here

API reference

Generated from OpenAPI — the authoritative endpoint list.

Set up the Co-Pilot

A guided walkthrough of the AI integration.