# Manager

> A multi-tenant operations hub. Websites, apps, APIs, scheduled jobs and AI agents
> push health, analytics, security, log and custom telemetry to one place, where it
> becomes status, freshness monitoring, alert rules and incidents.

You are most likely here because a service you operate should report into Manager.
Everything you need to do that is public. You need exactly one secret from a human:
a registration token, created by an owner or admin under "API & MCP" in the dashboard.

## Integration in three steps

1. Receive a registration token (starts with `mgr_reg_`). It is bound to one tenant
   and one stable service key.
2. POST a manifest to `https://monitor.skjldlabs.com/api/v1/register` with that token. The manifest declares
   the service and every data source, including reporting frequency, metrics, event
   types and tags. The response contains one-time ingest tokens for new sources.
3. Send telemetry with each source token, either over REST or over MCP. Both paths
   store the same events and drive the same incidents.

## Documents

- [https://monitor.skjldlabs.com/agents.md](https://monitor.skjldlabs.com/agents.md): the full integration contract in Markdown. Read this one.
- [https://monitor.skjldlabs.com/openapi.yaml](https://monitor.skjldlabs.com/openapi.yaml): OpenAPI description of the ingestion and mobile API.
- [https://monitor.skjldlabs.com/.well-known/mcp.json](https://monitor.skjldlabs.com/.well-known/mcp.json): MCP server discovery, tools and auth scheme.
- [https://monitor.skjldlabs.com/integrasjon](https://monitor.skjldlabs.com/integrasjon): the same contract as a web page, in Norwegian.
- [https://monitor.skjldlabs.com/en/integration](https://monitor.skjldlabs.com/en/integration): the same contract as a web page, in English.

## Endpoints

- `GET https://monitor.skjldlabs.com/api/v1/register`: Read back the manifest this registration token is bound to.
- `POST https://monitor.skjldlabs.com/api/v1/register`: Create or update the service and its data sources from a manifest. Returns one-time tokens for newly created sources.
- `POST https://monitor.skjldlabs.com/api/v1/register/sources/{source_key}/rotate-token`: Issue a new ingest token for one source of the same service.
- `POST https://monitor.skjldlabs.com/api/v1/ingest/{source_id}`: Send one telemetry event.
- `POST https://monitor.skjldlabs.com/api/v1/ingest/{source_id}/batch`: Send up to 100 events in one request, as an "events" array.
- `GET https://monitor.skjldlabs.com/api/v1/ingest/{source_id}/status`: Read the source status, when data last arrived and when the next report is expected.
- `POST https://monitor.skjldlabs.com/mcp/{source_id}`: Streamable HTTP MCP endpoint exposing the same ingestion path as REST.

## Authentication

Every request carries `Authorization: Bearer {TOKEN}`. Registration tokens manage the
manifest; source tokens send telemetry. They are different credentials and are stored
as SHA-256 hashes, so a lost token can only be replaced, never recovered.