Skip to content

The pull contract

GET /api/platform/v1/{dataset} - the one read API REM Auth, REM Blogs, REM CloudHub and REM Vibe Coder serve to the watch tower.

GET {base_url}/api/platform/v1/{dataset}?days=30
Authorization: Bearer <read-only service token>
{"daily": [{"day": "2026-11-17", "app": "rch", "metric": "signups", "dim": "", "value": 12}],
 "snapshots": {"<key>": {}},
 "events": [{"app": "rch", "id": "...", "kind": "feedback", "severity": "info", "title": "...", "summary": "...",
             "link": "https://remcloudhub.com/...", "org": "...", "actor_email": "...", "occurred_at": "2026-11-17T10:00:00Z", "data": {}}]}

Rules:

  • app is one of rch, vibecoder, payments, blogs, auth (an app's own alias such as rem-cloudhub or vcn is mapped). Unknown apps, metrics and snapshot keys are dropped.

  • dim narrows a number (model:<name>, org:<name>, form:<name>); "" is the total.

  • Send the last days days every time: rows are upserted per app, metric, day and dim. Today may be partial.

  • 401 or 403 = bad token; 404 = not implemented yet. Both show as the source's error.

Source

Serves

Dataset

Daily metrics

Snapshots

auth

REM Auth, rpt_ token

auth

signups signins signins_failed mfa_challenges mfa_enrolled_pct deletions active_users per product

funnel per app: signed_up, verified, first_sign_in, active, mfa_on, deleted

blogs

REM Blogs, rbp_ token

contacts

contacts_new (+ form: dims), contacts_contacted, contacts_closed, response_hours, contacts_pending

pending, oldest (no e-mails)

rch

REM CloudHub

events

events only

vibecoder

REM Vibe Coder

events

events only

REM Payments has no /api/platform/v1: the watch tower reads its admin API with a read-only ptk_ token (payments: revenue, purchases, checkouts, trials, refunds, failed payments, active subscriptions, plans and the checkout funnel; credits: spent, granted, clawed back, expired, balance, AI requests, tokens and cost, accounts, top payers, anomalies). Telemetry comes from the telemetry engine's query API with a viewer key.

Example against REM Auth:

curl "https://auth.remplatforms.com/api/platform/v1/auth?days=30" -H "Authorization: Bearer rpt_..."

A connect token (rat_) is refused there, and so is any other dataset.

Last updated 18 Nov 2026

The pull contract · REM Platforms Blog