---
title: "Diagnose your integration from the command line."
url: "https://platformdocs.coinme.com/#/build/web/doctor"
markdown: "https://platformdocs.coinme.com/pages/build/web/doctor.md"
summary: "framekit-doctor ships with the SDK. It answers the two questions every integrator eventually asks: did I implement this correctly? and why doesn't my deployed integration work? Nothing to mount on your site, nothing to deploy; it runs from your terminal. If `framekit-doctor` is not found, update @coinme/coinme-bridge-framekit (the CLI ships with every stable release)."
surface: "ramp"
platform: "web"
package: "@coinme/coinme-bridge-framekit"
version: "1.1.2"
peerDependencies: {"react":">=18.0.0","react-dom":">=18.0.0"}
---

# Diagnose your integration from the command line.

**framekit-doctor** ships with the SDK. It answers the two questions every integrator eventually asks: **did I implement this correctly?** and **why doesn't my deployed integration work?** Nothing to mount on your site, nothing to deploy; it runs from your terminal. If `framekit-doctor` is not found, update @coinme/coinme-bridge-framekit (the CLI ships with every stable release).

## 1. Check your code

Static analysis of your project. Zero extra dependencies; failures print the file, the line, and the fix.

```bash
# From your project root (the SDK ships the CLI):
yarn framekit-doctor check .

# Or without installing anything first:
npx -p @coinme/coinme-bridge-framekit framekit-doctor check .
```

### What check looks for

- The SDK is installed and the @coinme registry is configured
- CoinmeFrame / createCoinmeFrame is actually mounted somewhere
- Credentials are real, not placeholders (demo-ramp, your-ramp-id, ...)
- The Orchestrator URL uses HTTPS (or loopback for local dev)
- Foot-guns: hand-rolled iframe sandbox attributes, Referrer-Policy: no-referrer, CSP metas that block the widget

## 2. Probe your deployed integration

The probe drives a headless Chromium at your real page, so the browser genuinely is your origin. It watches the iframe, your CSP as actually enforced, your response headers, and the live bridge traffic; a passing bridge-session check empirically proves your hostname is in the Orchestrator embed allowlist.

```bash
# One-time: the probe drives your locally installed Chrome
yarn add -D playwright-core

# Point it at any deployed (or local) integration:
yarn framekit-doctor probe https://your-deployed-host.example

# Useful flags:
#   --orchestrator <origin>   pin a non-standard widget origin
#   --timeout <ms>            wait budget (default 15000)
#   --json                    machine-readable output for CI
```

## What a healthy probe looks like

```
framekit-doctor probe https://your-deployed-host.example

PASS    Page reachable
        https://your-deployed-host.example responded with HTTP 200.
PASS    Widget iframe present
        An iframe pointed at https://widget.coinme.com exists on the page.
PASS    Host CSP
        The CSP in effect permitted the widget iframe.
PASS    Referrer policy
        Referrer-Policy is browser default; the widget can recognise your site.
PASS    Bridge session
        Bridge traffic beyond the handshake was observed from
        https://widget.coinme.com; the session is established, which also
        proves your-deployed-host.example is on the embed allowlist.

All checks passed.
```

Exit codes are CI-friendly: 0 when everything passes, non-zero when anything fails, and `--json` emits the same report machine-readably. Run `check` before your first commit and `probe` against every environment you deploy; remember the [allowlist requirement](https://platformdocs.coinme.com/pages/build/web/how-to-use.md): a passing local test proves nothing about production until your hostname is on the allowlist.
