---
title: "Browser Request Login"
method: POST
path: "/api/agents/internal/browser/request-login"
tags: ["agent-internal"]
---

# Browser Request Login

`POST /api/agents/internal/browser/request-login`

## Request

- Base URL: `https://api.maritime.sh` (the document declares no server; this is the origin it was published from)
- URL: `https://api.maritime.sh/api/agents/internal/browser/request-login`
- Auth: none declared

Open a Browserbase Live View session for the agent and DM the
user the URL via Telegram (optionally) so the user can interactively
log in to a third-party site.

Works for both Maritime-pool agents AND agents with user-supplied
BROWSERBASE_API_KEY + BROWSERBASE_PROJECT_ID. For BYO-key agents,
the session is created under the user's own Browserbase account
so cookies set during the takeover persist into the agent's later
MCP sessions.

Body (all optional): `{"service": "facebook"}`, a descriptor used in
the DM text. No state-tracking; session lives ~10 min on Browserbase's
side, then auto-expires.

Returns 200 with `{session_id, live_view_url, expires_at, telegram_delivered}`.
Errors:
  - 401: bad/missing internal token
  - 404: agent not found
  - 503: agent has no Browserbase credentials (no BYO key AND no pool)
  - 502: Browserbase API call failed

## Headers

- `X-Maritime-Agent-Id` string, nullable
- `authorization` string, nullable

## Request body

- object

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/maritime/apis/maritime-api.md) - [All operations](https://skmtc.dev/maritime/apis/maritime-api/llms.txt) - [OpenAPI document](https://skmtc.dev/maritime/apis/maritime-api/revisions/acd712090ad6?raw)