open-index/open-npm huggingface dataset:
npm package: @mercury-tech-dev/nestjs-schematics
Description: MTD Custom Nest - modern, fast, powerful node.js web framework (@schematics)
Latest version: 1.0.4

# MTD
Custom version for Mercury Technology Development
## Description

In order to help people manage their projects, the CLI tool has been created. It helps on many grounds at once, from scaffolding the project to build well-structured applications. The Nest CLI is based on the [@angular-devkit](https://github.com/angular/devkit) package. Also, there're special schematics that are dedicated to the Nest development [@nestjs/schematics](https://github.com/nestjs/schematics).


## Installation
### NPM:

```
$ npm install -g @nestjs/schematics
```

### Docker:
```
$ docker pull nestjs/cli[:version]
$ docker run -it -rm -p 3000:3000 -v $(pwd)/workspace nestjs/schematics[:version]
```

### GIT:
```
$ git clone https://github.com/nestjs/schematics.git <project>
$ cd <project>
```

With your Node runtime:
```
$ npm install
$ npm link
```

With Docker:

```
$ docker build -t nestjs/schematics .
```

## Usage

Learn more in the [official documentation](https://docs.nestjs.com/).

## Stay in touch

* CLI Author - [Thomas Ricart](https://github.com/ThomRick) and [Kamil Mysliwiec](https://github.com/kamilmysliwiec)
* Website - [https://nestjs.com](https://nestjs.com/)
* Twitter - [@nestframework](https://twitter.com/nestframework)
npm package: @mercuryo-ai/agentbrowse-cli
Description: Browser automation CLI for AI agents
Latest version: 0.1.12

# @mercuryo-ai/agentbrowse-cli

[![npm version](https://img.shields.io/npm/v/@mercuryo-ai/agentbrowse-cli)](https://www.npmjs.com/package/@mercuryo-ai/agentbrowse-cli) [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Node.js >= 18](https://img.shields.io/badge/node-%3E%3D18-brightgreen.svg)](https://nodejs.org)

Browser automation from the command line — built for AI agents.

AgentBrowse CLI lets an agent (or a human operator) drive a real browser
session: launch or attach, inspect the page, click and type on visible
controls, navigate, extract structured data, and capture screenshots.

It works well on its own for general browser tasks. When a workflow later
reaches a login, identity, or payment step that requires stored credentials,
pair it with MagicPay.

By default the CLI returns a compact JSON contract for machine consumers.
Add `--verbose` for a broader diagnostic payload with automatic redaction of
sensitive values.

Open source: [github.com/MercuryoAI/agentbrowse](https://github.com/MercuryoAI/agentbrowse)

## Install

```bash
npm i -g @mercuryo-ai/agentbrowse-cli@latest
```

## Core Loop

1. `agentbrowse launch [url]` or `agentbrowse attach <cdp-url>`
2. `agentbrowse observe`
3. `agentbrowse act <targetRef> <action> [value]`
4. repeat `observe` after meaningful page changes
5. `agentbrowse navigate <url>` if the destination is already known
6. `agentbrowse extract '<schema-json>' [scopeRef]` when you need structured
   output
7. `agentbrowse screenshot` or `agentbrowse browser-status` for evidence and
   debugging
8. `agentbrowse close` when you are done

## When You Need API Setup

Simple browser tasks work without API setup.

Goal-based `observe` and `extract` use the shared agent config. Set it up once
with:

```bash
agentbrowse init <api-key>
```

You can also provide `MAGICPAY_API_KEY` in the environment. Use
`agentbrowse doctor` only if semantic commands still fail after `init` and you
want to inspect `~/.magicpay/config.json`.

## First Task

Start with a plain browser task:

```bash
agentbrowse launch "https://example.com"
agentbrowse observe
agentbrowse --verbose browser-status
```

If you want a focused or structured result:

```bash
agentbrowse init <api-key>
agentbrowse observe "find the next visible action to continue"
agentbrowse extract '{"summary":"string"}'
```

By default, AgentBrowse emits the essential JSON contract for external
consumers. Use `--verbose` when you need the broader diagnostic payload with
safe redaction:

```bash
agentbrowse observe --verbose
agentbrowse browser-status --verbose
```

## Command Groups

- Session setup: `launch`, `attach`, `navigate`
- Page work: `observe`, `act`, `extract`
- Diagnostics and cleanup: `screenshot`, `browser-status`, `close`
- Semantic runtime setup: `init`, `doctor`, `--version`

## Companion Tools

- If the page is already at a protected login, identity, or payment form:
  use `@mercuryo-ai/magicpay-cli`
- If one CLI should cover both browser work and protected fills:
  use `@mercuryo-ai/magicpay-agent-cli`
npm package: @mercuryo-ai/captcha-solver
Description: Captcha-solving runtime primitives for MagicPay and agent workflows
Latest version: 0.1.2

# @mercuryo-ai/captcha-solver

Standalone captcha-solving runtime primitives.

This package owns the captcha-specific execution layer that should not live in
`@mercuryo-ai/agentbrowse` and is not part of the long-term MagicPay payment SDK
surface.

It currently provides:

- browser-connected captcha solving via `solveCaptchasByCdp(...)`
- low-level solver client `CaptchaSolver`
- detection and solving helpers for reCAPTCHA v2, hCaptcha, and Turnstile

It does not provide:

- browser session persistence
- MagicPay CLI orchestration
- payment/session/approval flow semantics

## Install

```bash
npm i @mercuryo-ai/captcha-solver
```

## Example

```ts
import { solveCaptchasByCdp } from '@mercuryo-ai/captcha-solver';

const result = await solveCaptchasByCdp('ws://127.0.0.1:9222/devtools/browser/test', 'ap_test', {
  apiUrl: 'https://agents-api.mercuryo.io/functions/v1/api',
  timeoutMs: 90_000,
});

console.log(result);
```
npm package: @mercuryo-ai/magicpay-agent-cli
Description: MagicPay Agent CLI — combined browser and payment orchestration shell
Latest version: 0.1.2

# @mercuryo-ai/magicpay-agent-cli

Branded combined CLI for MagicPay browser and payment orchestration.

`magicpay-agent` is the combined MagicPay CLI surface for:

- gateway setup and health checks;
- workflow session lifecycle;
- secret catalog, request, poll, protected fill, and guarded submit/observe flow;
- CAPTCHA solving via `@mercuryo-ai/captcha-solver`;
- browser-oriented command UX built on top of `@mercuryo-ai/agentbrowse`.

## Install

```bash
npm i -g @mercuryo-ai/magicpay-agent-cli
magicpay-agent --help
```

## Current surface

- `init`
- `status`
- `launch`
- `attach`
- `browser-status`
- `start-session`
- `end-session`
- `find-form`
- `navigate`
- `observe`
- `act`
- `extract`
- `screenshot`
- `close`
- `get-secrets-catalog`
- `request-secret`
- `poll-secret`
- `fill-secret`
- `submit-form`
- `solve-captcha`

Browser attach happens over CDP:

- `magicpay-agent attach <cdp-url>`

`magicpay-agent fill-secret` now performs a post-fill refresh, auto-submits
when it can resolve one live form-bound submit control, and returns a
follow-up observe result when submission happens. `submit-form` remains
available as a manual recovery surface.

`magicpay-agent status` stays quiet about CLI updates by default. When a newer npm
release is available, it includes a short English notice and the suggested
update command.

## Architecture boundary

- `magicpay-agent` is the combined operator CLI for browser flows, workflow
  sessions, approvals, and protected secret handling.
- `@mercuryo-ai/agentbrowse` owns browser primitives and the reusable browser
  session store API.
- `@mercuryo-ai/magicpay-sdk` owns reusable MagicPay API and flow helpers.
- `@mercuryo-ai/magicpay-agent-cli` owns combined CLI orchestration, shared-home
  wiring under `~/.magicpay`, and the union browser plus payment command UX.
npm package: @mercuryo-ai/magicpay-home
Description: Internal shared local home/config/state contract for MagicPay product CLIs
Latest version: 0.1.8

# @mercuryo-ai/magicpay-home

[![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

Shared configuration and state management for the MagicPay CLI family.

This package owns the `~/.magicpay` directory contract — configuration files,
browser session state, and workflow persistence — used by all three MagicPay
CLIs:

- [`@mercuryo-ai/agentbrowse-cli`](https://www.npmjs.com/package/@mercuryo-ai/agentbrowse-cli) — browser automation
- [`@mercuryo-ai/magicpay-cli`](https://www.npmjs.com/package/@mercuryo-ai/magicpay-cli) — protected-form fills
- [`@mercuryo-ai/magicpay-agent-cli`](https://www.npmjs.com/package/@mercuryo-ai/magicpay-agent-cli) — combined browser + payment agent

## Do I need to install this?

No. This package is pulled in automatically as a dependency of the CLIs above.
You don't need to install or configure it directly.

## What it provides

- Typed helpers for `~/.magicpay/config.json` (API key, endpoints, feature
  flags)
- Browser session persistence across process restarts
- Workflow state tracking for multi-step protected-form flows
- Atomic filesystem writes to prevent corruption from concurrent CLI runs

## License

[MIT](LICENSE)
npm package: @mercuryworkshop/proxy-transports
Description: A universal interface for designing "transports", i.e. ways of sending https+wss traffic from the browser through a proxy.
Author: Mercury Workshop
Latest version: 1.0.2

# Proxy Transports

A universal interface for designing "transports", i.e. ways of sending https+wss traffic from the browser through a proxy.

A transport is an object that implements the `ProxyTransport` interface.

```js
export interface ProxyTransport {
	init: () => Promise<void>;
	ready: boolean;
	connect: (
		url: URL,
		protocols: string[],
		requestHeaders: RawHeaders,
		onopen: (protocol: string, extensions: string) => void,
		onmessage: (data: WebSocketDataType) => void,
		onclose: (code: number, reason: string) => void,
		onerror: (error: string) => void
	) => [
		(data: WebSocketDataType) => void,
		(code: number, reason: string) => void,
	];

	request: (
		remote: URL,
		method: string,
		body: BodyInit | null,
		headers: RawHeaders,
		signal: AbortSignal | undefined
	) => Promise<TransferrableResponse>;
}
```

Successor to [bare-mux](https://github.com/MercuryWorkshop/bare-mux)
npm package: @mere1y/effector-openapi-preset
Description: Generate API layer from Swagger by openapi
Author: Sergey Sova
Latest version: 0.4.2

# openapi-preset-effector

## Usage

#### Install openapi and preset

```shell
yarn add -D openapi@^1.0.0 openapi-preset-effector
```

#### Create config

```js
// openapi.config.js
module.exports = {
  file: 'path to local or remote swagger v2 or v3 spec',
  outputDir: 'relative path to generated api directory',
  presets: ['openapi-preset-effector'],
};
```

#### Options

```js
// openapi.config.js
module.exports = {
  file: 'path to local or remote swagger v2 or v3 spec',
  outputDir: 'relative path to generated api directory',
  presets: [
    [
      'openapi-preset-effector',
      {
        effectorImport: 'effector-root',
        requestName: 'fetchFx',
        requestPath: '../lib/fetch',
      },
    ],
  ],
};
```

- `effectorImport` (default `"effector"`) — what instance of the effector should be used
- `requestName` (default `"requestFx"`) — change base effect for the each request
- `requestPath` (default `"./request"`) — whether to import base request from

#### Run generation

```shell
yarn openapi
# or
npx openapi
```

#### Review generated files

```shell
ls -la ./path-to-generated-api
```