Send your own data

Use this page if you write a program that sends measurements to VibeMon or reads them. To monitor coding tools, servers, or Kubernetes, use the installers in the guides instead.

Before you start

1. Open Account & tokens and select Create token.
2. Choose Write to send data or Read to read data, then select Show token and copy it.
3. Keep the token in an environment variable or a secret manager. Do not put it in a URL or in your code.

Send the token in every request:

Authorization: Bearer vm_…
Content-Type: application/json

Send a resource

To define a resource on the web first, open Add resource. The page gives you a request template.

Send POST https://vibemon.io/api/v1/ingest with a write token at least every 60 seconds:

{
  "sourceId": "freezer-1",
  "kind": "resource",
  "resourceType": "Cold storage",
  "displayName": "Warehouse freezer",
  "statusMessage": "Cooling",
  "observedAt": "2026-10-09T12:00:30.000Z",
  "health": "ok",
  "metricDefinitions": {
    "temperature": { "label": "Temperature", "unit": "°C", "display": "gauge", "min": -40, "max": 20 },
    "power": { "label": "Power", "unit": "W", "display": "number", "min": 0 }
  },
  "metrics": { "temperature": -12, "power": null }
}

Replace the example observedAt with the current measurement time for every request; sending the dated example unchanged is rejected. Creating a template on Add resource does not save a live resource: its first accepted report does.

Send the definitions with every request. The whole request must be 16 KiB or less.

A successful request returns { "accepted": true }. An observation that is not newer than the last one returns { "accepted": false, "reason": "duplicate_or_older" }. After a network failure, send only the newest observation.

To change the labels, units, ranges, or order later, use Edit resource and metrics on the dashboard. Your program does not overwrite these settings.

Send coding-agent activity

For a coding tool that VibeMon does not support, send the state of each project:

{
  "sourceId": "agent:workstation-my-project",
  "kind": "agent",
  "displayName": "my-project",
  "observedAt": "2026-10-09T12:00:30.000Z",
  "health": "ok",
  "account": { "provider": "mytool", "id": "work", "displayName": "My tool (work)" },
  "agent": { "state": "working", "character": "vibemon", "project": "my-project" },
  "metrics": { "contextPercent": 42 }
}

• agent.state, agent.character, and agent.project are required. character is a VibeMon character name, such as vibemon.
• state: start, idle, thinking, planning, working, packing, notification, done, sleep, or alert.
• account.provider: 1–32 characters. A lowercase letter first, then lowercase letters, digits, _, or -. account.id follows the sourceId rules, and account.displayName has 1–128 characters. Each provider and id pair is one coding account.
• metrics: optional contextPercent, usageSessionPercent, and usageWeekPercent, from 0 to 100.
• While a long task runs, send the same state every 60 seconds with "heartbeat": true.

Connect coding account generates the account values for you.

Read data

Use a read token:

Each source has the last observation, receivedAt, and stale. A resource is stale 120 seconds after its last report.

Limits and errors

All tokens of one account share 240 write requests and 600 read requests per minute.