Vexo Developer Docs

Start here

Four routes into the platform. Each one ends with data you can ship.

5 min

Quickstart

Pair a ring, request a grant, stream your first capture. Five steps, about five minutes.

OAuth 2.1

Authentication

Scoped tokens that keep the wearer in the loop for every grant, and die with it.

REST · WS

Captures API

Write a moment of consented context once, then fan it out wherever the wearer allows.

MCP

MCP Marketplace

Publish a context server so agents can use Vexo data, with the wearer holding the keys.

Core concepts

Three ideas carry the whole platform. Everything else is detail.

Biometric stream

Six signal families, sampled on the finger and fused on-device. The API serves derived metrics only, typed end to end.

Distribution loop

A capture is written once, then fans out to every destination the wearer allows: apps, webhooks, MCP servers.

Consented marketplace

Context servers run behind explicit, revocable scopes. Nothing leaves the ring without a grant.

Your first capture

One authenticated stream call. Every event is already inside the wearer's grant, so there is nothing to filter.

Stream captures

stream.ts

import { Vexo } from "@vexoring/sdk";

const vexo = new Vexo({ token: process.env.VEXO_USER_TOKEN });

// Streams every capture the wearer's grant lets you see.
for await (const capture of vexo.captures.stream({ wearer: "wr_7h2m4q" })) {
  console.log(capture.id, capture.signals);
  // cap_01j8ac3v9d  { hrv: 61, hr: 58, temp: 33.4 }
}