Documentation

Web

Add one script tag before the closing body tag on every page you want watched:

<script src="https://probie.dev/assets/probie-widget.js" data-token="YOUR_WIDGET_TOKEN"></script>

This bundle renders a small "Report an issue" button and loads the passive collector. For capture with no visible UI, load the collector on its own:

<script src="https://probie.dev/assets/probie-widget-events.js" data-token="YOUR_WIDGET_TOKEN"></script>

Client-rendered apps (React, Next.js, Vue) inject the same tag once on the client; there is no npm package for the web SDK. After load, attribute sessions to a signed-in user with window.probie('identify', userId).

Expo and React Native

The SDK targets the Expo managed workflow, SDK 50 and later, and has no runtime dependencies.

npx expo install @probie-dev/react-native

import { ProbieProvider } from '@probie-dev/react-native';

export default function RootLayout() {
  return (
    <ProbieProvider config={{ token: 'YOUR_WIDGET_TOKEN', apiBase: 'https://probie.dev' }}>
      {/* your app */}
    </ProbieProvider>
  );
}

The provider captures JavaScript errors, unhandled promise rejections, network failures, and app lifecycle on its own. Screens, taps, and form friction are opt-in hooks documented in the package README on npm.

Swift (macOS and iOS)

The Swift package supports macOS 12 and iOS 15 and later. Instrumentation is explicit; there is no method swizzling.

.package(url: "https://github.com/ProbieAI/probie-swift", from: "0.1.0")

import Probie

Probie.start(.init(token: "YOUR_WIDGET_TOKEN", apiBase: "https://probie.dev"))

Then mark what matters: .probieScreen("Checkout") and .probieTap("buy") on SwiftUI views, Probie.form("signup") for form friction, Probie.captureError(error) in catch blocks, and URLSession(configuration: Probie.instrumented(.default)) for failing requests.

Install with a coding agent

The integration skill at https://probie.dev/skill is a SKILL.md file that walks a coding agent through registration and installation. The agent infers the project name, asks its human for an email and whether limited setup/product follow-up is allowed, provisions a token, installs it, verifies one passive event, and reports the emailed/browser claim flow. Point Claude Code, Cursor, or any agent that reads skills at it, or save it into the repository:

curl -fsSL https://probie.dev/skill -o .claude/skills/probie-integration/SKILL.md

The registration endpoint is POST /api/agent/registrations; it requires email, boolean contact_consent, and a high-entropy Idempotency-Key header. Omit project_name for inspection access, or include it to provision an integration. Every response includes a dispatch token and signed seven-day claim URL; integration responses also include widget and skill credentials. The MCP tools are split by task: register_inspection_access for inspecting only and register_integration for installing Probie.

HTTP API

Inspecting only: first register inspection access by omitting project_name. Installing Probie: include project_name in the same registration request. Keep the returned dispatch token secret.

curl -s -X POST https://probie.dev/api/agent/registrations \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: A_RETAINED_RANDOM_VALUE_AT_LEAST_32_CHARS' \
  -d '{"email":"[email protected]","contact_consent":false}'

Then start an inspection with the dispatch token as a bearer credential. The endpoint allows cross-origin requests.

curl -s -X POST https://probie.dev/api/dispatch \
  -H 'content-type: application/json' \
  -H 'Authorization: Bearer YOUR_DISPATCH_TOKEN' \
  -d '{"url": "example.com"}'

202

{"id": 123, "statusUrl": "...", "pageUrl": "..."}. A new inspection was queued.

200

The same fields plus "reused": true. The website already had a live inspection and you were attached to it.

400

{"error": "..."}. The body was not JSON, had no url, or named a private or reserved address.

401

{"error": "Unauthorized"}. The bearer token was missing, invalid, expired, or revoked.

429

{"error": "...", "retryAfterSecs": n} with a Retry-After header. The hourly limit was reached.

Poll statusUrl (GET /dispatch/{id}/status) every 5 seconds or so. The payload depends on the state:

queued or running

{"status", "progress", "queuedAhead", "activity": [...], "chips": {...}}. activity is a short plain-language log.

ok

{"status": "ok", "reportUrl": "/report/<id>/<slug>"}. The report is ready.

error or skipped

{"status", "failureMessage", "allowUrl"}. skipped means a bot wall stopped Probie; allowUrl explains how to let it through.

MCP server

The same surface is available to agents as a remote MCP server at https://probie.dev/mcp. It uses Streamable HTTP. Registration and status reads are public; starting an inspection requires the dispatch token returned by registration. Add it to a client:

{
  "mcpServers": {
    "probie": { "type": "http", "url": "https://probie.dev/mcp" }
  }
}

claude mcp add --transport http probie https://probie.dev/mcp

register_inspection_access

Inspecting only: register an email-bound dispatch identity without creating a project.

register_integration

Provision a widget token after collecting the human’s email and consent choice. Requires a retained idempotency key and returns a seven-day claim URL.

inspect_website

Start an inspection with a dispatch token. Returns the id and the URLs to poll and open; reuses live and recent inspections.

get_inspection

The state of an inspection by id, with absolute report and allow URLs when it has finished.

get_integration_skill

The integration skill, with the token filled in when a widget token is passed.

probie://skill

The generic integration skill as a text/markdown resource.

Usage limits apply to inspection and registration across both REST and MCP. A rate-limited response tells the caller when to retry.