Introduction
What Evercam offers developers, and which API does what.
Evercam captures, stores and interprets visual data from construction sites. Everything you can see in the Evercam dashboard is available over plain HTTP, so you can build the same experiences into your own applications.
The shape of the platform
The platform splits into two kinds of API. Platform APIs serve data you read — projects, cameras, snapshots, recordings and analysis. Ingest APIs accept data you send — 360 captures, BIM models and drone flights.
One token, several APIs
The JWT returned by the Dash API's login endpoint is also accepted by the AI API and Labs. You authenticate once and use the same credential across them.
Your first request
Every request is ordinary HTTP. Authenticate, then call an endpoint:
Exchange an email and password for a JWT.
curl -X POST "https://media.evercam.io/v2/auth/login" \
-H "Content-Type: application/json" \
-d '{"username": "you@example.com", "password": "…"}'The response contains your user record and a token field. Send that token as
a bearer credential on subsequent requests:
curl -H "Authorization: Bearer $EVERCAM_TOKEN" \
"https://media.evercam.io/v2/projects"Building for an AI agent
The same platform is also available over the
Model Context Protocol, so an agent can read
your cameras, footage and analytics as callable tools rather than HTTP routes.
The hosted server is https://mcp2.evercam.io/mcp. Assistants such as Claude,
Codex, Cursor or ChatGPT sign in to it with your own Evercam account over OAuth,
and your own code can use the token above instead. See
The MCP server for what it exposes and
Connect a client for the
per-client steps.
Where to go next
Read Authentication for the details of each API's credential format, then browse the API reference for every available operation.