Authentication

All Meshbrow API requests require authentication via an API key.

API Keys

API keys are prefixed with mb_live_ (production) or mb_test_ (sandbox). Pass your key in the Authorization header:

Authorization: Bearer mb_live_your_key_here

CLI Authentication

The fastest way to authenticate the CLI is the browser flow:

meshbrow auth login

This opens your browser to meshbrow.dev/cli/authorize. Confirm the code shown in your terminal matches the one in the browser, click Authorize, and the CLI completes automatically — an API key is generated for your account and saved to ~/.meshbrow.yaml. To authenticate without a browser (CI, headless servers), pass a key directly:

meshbrow auth login --key mb_live_your_key_here

SDK Authentication

import { Meshbrow } from '@meshbrow/sdk';

const client = new Meshbrow({
  apiKey: process.env.MESHBROW_API_KEY,
});

Key Security

Never commit API keys to source control. Use environment variables or a secrets manager.

Best practices:

Store keys in environment variables (MESHBROW_API_KEY)
Use different keys for development and production
Rotate keys periodically via the dashboard
Restrict key permissions by scope (sessions, fleet, billing)

Rate Limits

Plan	Requests/min	Concurrent Sessions
Free	60	5
Pro	600	50
Enterprise	6000	500

Rate limit headers are included in every response:

X-RateLimit-Limit: 600
X-RateLimit-Remaining: 594
X-RateLimit-Reset: 1700000060

Error Responses

Authentication errors return 401 Unauthorized:

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or expired API key"
  }
}

Getting Started

Core Concepts

Authentication

Authentication

API Keys

CLI Authentication

SDK Authentication

Key Security

Rate Limits

Error Responses

​Authentication

​API Keys

​CLI Authentication

​SDK Authentication

​Key Security

​Rate Limits

​Error Responses

Authentication

API Keys

CLI Authentication

SDK Authentication

Key Security

Rate Limits

Error Responses