What makes lobstercash notable?

1.9K downloads. Trust evidence available

How should lobstercash be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

lobstercash

Use this skill when the user wants to spend money, make purchases, send crypto, pay for APIs, browse websites for shopping, complete checkout, or manage an A...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.9k

Updated

Oct 9, 2026

Version

0.0.16

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.9K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 1.9K downloadsadoption · observed Oct 9, 2026
Latest release: 0.0.16release · observed May 4, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s176gxg53nmy7n4z5dq80hfst583h1en:lobstercash

Install using `clawhub skill install s176gxg53nmy7n4z5dq80hfst583h1en:lobstercash` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/manu-xmint/lobstercash before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-manu-xmint-lobstercash/snapshot"

Documentation

CLAWHUB

152,616 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: lobstercash
description: 'Use this skill when the user wants to spend money, make purchases, send crypto, pay for APIs, browse websites for shopping, complete checkout, or manage an AI agent''s payment wallet. Covers buying products online with credit cards (with browser-automated checkout when available, or driven by the agent''s own browser tooling otherwise), sending tokens, paying for x402 protocol APIs, checking balances, depositing funds, browsing available services, and signing on-chain transactions — all with secure guardrails, and appropriate human controls. Trigger on any spending, wallet, or shopping intent: "buy this", "pay for that", "send tokens", "how much do I have", "what can I buy", "top up my wallet", "get a card", "set up payments", "find me something to buy", "complete the checkout", or "browse that site" — even if the user doesn''t mention "lobster", "crypto", or "Solana" directly.'
metadata:
version: "0.0.16"
---

# Lobster Cash CLI Skill

The Lobster Cash CLI (`lobstercash`) gives AI agents payment tools — a blockchain wallet, virtual cards for buying anything online, optional cloud browser automation for browsing sites and completing checkout, and x402 protocol support for paying APIs — all with human approval in the loop. Use `lobstercash <command> --help` for full flag details on any command.

## Installation

Install globally:

```bash
npm install -g @crossmint/lobster-cli
```

After installation, all commands are available via the `lobstercash` binary.

## Steps to use this skill

### 1. Version check (automatic)

The CLI automatically checks for updates on every API call. If an update notice appears in the command output, tell the user and offer to run `npm update -g @crossmint/lobster-cli`. If the notice says the update is **required**, you must also update the skill from https://www.lobster.cash/install before continuing. Do not run separate version-check commands.

### 2. Select lobstercash agent to use

Every lobstercash command operates on the **active agent**. Before doing anything else, make sure the right agent is selected.

```bash
lobstercash agents list
```

Then follow this decision tree:

1. **You see yourself in the list and it says `(active)`** → You're good. Move on.
2. **You see yourself in the list but it's NOT active** → Run `lobstercash agents set-active <agentId>` with the matching ID, then move on.
3. **No agent matches you** (or the list is empty) → Register a new one. Read the [agents reference](references/agents.md) for how to register one.

**How to recognize yourself:** Match by name. If you are Claude Code, look for an agent named "Claude Code" or similar. Same for Cursor, Codex, Gemini, etc. If you aren't sure, ask the user which agent to use.

### 3. Route based on the user's intent

Determine which scenario applies and follow the corresponding section:

- **A) Buy something online** (product, subscription, domain, service) → [Buy something online](#a-buy-something-online)
-

_meta.json

{
  "ownerId": "kn7dhdwzdnx02w37wfnqkq6df180b5ap",
  "slug": "lobstercash",
  "version": "0.0.16",
  "publishedAt": 1777925289336
}

references/agents.md

# Agents — Register, List, and Switch Agents

Manage agents registered on the server. An agent must exist before running any other command.

## Register an agent

```bash
lobstercash agents register --name "<name>" [--description "<desc>"] [--image-url "<url>"]
```

Registers a new agent on the server and sets it as the active agent locally.

- `--name` **(required)** — A **unique, descriptive, human-readable display name**. Use natural casing with spaces, not dashes. Do **not** use generic names like `"My Agent"` or `"Assistant"`.
- `--description` **(recommended)** — A short summary of what the agent does. This is shown to the user during approval.
- `--image-url` **(recommended)** — An avatar or logo URL for the agent. This is displayed alongside the agent's name in the dashboard and approval screens. Preset logos for well-known agents are hosted at `https://lobster.cash/agent-avatars/`:

| Agent | URL |
| ----------- | ---------------------------------------------------- |
| Claude Code | `https://lobster.cash/agent-avatars/claude-code.svg` |
| Cursor | `https://lobster.cash/agent-avatars/cursor.svg` |
| Codex | `https://lobster.cash/agent-avatars/codex.svg` |
| Gemini | `https://lobster.cash/agent-avatars/gemini.svg` |
| OpenClaw | `https://lobster.cash/agent-avatars/openclaw.svg` |

Use a URL from this table, a URL the user explicitly provided, or omit `--image-url` entirely. Do **not** invent or guess image URLs — a broken avatar is worse than no avatar.

- `--network` **(optional)** — The blockchain the agent will operate on. Defaults to `base`. Accepts `base` or `solana`. **Most users should not change this.** Only pass `--network solana` when the user has explicitly asked for Solana, or when the context clearly implies the agent needs to operate on Solana (e.g. the task is to use a Solana-only integration like Jupiter or xStocks). See [Advanced: choosing a non-default chain](#advanced-choosing-a-non-default-chain).

#### Choosing a good name

Pick the name that will be most recognizable to the user on the dashboard and in approval prompts. Use your judgment — there is no single formula.

- **If you have a well-known identity, prefer that.** Agents with established names should use them: `"Claude Code"`, `"Devin"`, `"Cline"`, `"OpenClaw"`, or whatever the user already knows you as. If the user has configured a custom display name for you, use that.
- **If a task-specific name is more useful, use that instead.** When you are purpose-built for a particular job — shopping, research, scheduling — a descriptive name like `"Alice's Shopping Assistant"` or `"Travel Planner"` may be clearer than a generic runtime name.
- **When in doubt, combine both.** Something like `"Claude Code — Research"` works if you want to convey both identity and purpose.

The goal: when the user sees the name on an approval screen, they should immediately know

references/balance.md

# Balance

Check the current token balances in the agent wallet.

## Command

```
lobstercash crypto balance
```

## Reading the output

The output includes a `chain` field (e.g. `base`, `solana`) indicating
which network the balances are on, followed by one line per token in the
format `  <token>: <amount>`, e.g. `  usdc: 42.50`. Common tokens: `usdc`, plus
the chain's native token (`eth` on Base, `sol` on Solana).

Use the `chain` field to know which network the funds live on — this matters
when deciding parameters for `send` or `x402 fetch`.

Amount is a decimal string. Parse it as a float for arithmetic. Do not
display more than 2 decimal places to the user.

If the output says "No balances found": the wallet exists but holds no
tokens. Say "Your wallet is empty" not "wallet not found."

## When to run this skill

- Before every `send` command — check the balance covers the amount.
- Before every `x402 fetch` — check there is enough USDC.
- When the user asks "how much do I have" or similar.
- When diagnosing why a transaction failed.

## Insufficient balance

If the balance is too low for what the user wants to do:
Say: "Your wallet has [X] USDC. This needs [Y] USDC."
Then use `lobstercash crypto request --amount <needed> --description "<reason>"` to
generate a funding request link for the user.

Do not attempt the operation with insufficient funds. The error message
from the CLI in that case is technical and confusing to users.

references/cards-request.md

# Cards Request — Virtual Card for Purchases

Request a virtual card backed by the user's credit card. This is the fastest payment path — no USDC or wallet funding needed. If the wallet isn't configured yet, this command bundles setup automatically.

## Command

```bash
lobstercash cards request --amount <amount> --description "<description>" --period <period>
```

## What you need before running

Extract from context — do not ask if already clear:

- `amount`: how much to load in USD (e.g. `25.00`)
- `description`: what the card will be used for (e.g. `"AWS credits"`)
- `period`: billing period for the mandate — **required**, one of `weekly`, `monthly`, `yearly`. If the user doesn't specify, ask them.

If the user said "I need a card for $25 for AWS" you already have both.

## Reading the output

The output contains:

- `agentId`: the agent this card is for
- `amount`: the requested amount
- `period`: the billing period (`weekly`, `monthly`, or `yearly`)
- `description`: what the card is for
- `approvalUrl`: the URL the user must open to approve
- `setupSessionId`: present if wallet setup was bundled (first-time use)

## After running

Show the approval URL to the user:

> To create this card I need your approval. Open this link:
>
> [approvalUrl]
>
> Come back here when you've approved it.

Do not proceed until the user confirms they have approved.

## After user approves

Run `lobstercash cards list` to verify the card was created. Then proceed with the user's task — see `references/cards.md` for listing, revealing credentials, and checkout.

## Gotchas

- Virtual cards do NOT require USDC — they're backed by the user's credit card
- If the wallet isn't configured, setup is bundled automatically — do not run `lobstercash setup` first
- Only use this when the integration supports `card` payments — do not recommend for crypto-only integrations
- Write operation — do not retry automatically or if the user declines

Github ReposUpdated 6h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.