ClawCard icon

ClawCard

ClawCard gives AI agents a dedicated identity stack: email, US phone number, virtual cards, wallet, on-chain identity, and paid API access.

ClawCard

What ClawCard is

ClawCard is an identity and payment platform for AI agents. It gives an agent a dedicated email inbox, US phone number, virtual cards, a wallet, on-chain identity, and access to paid APIs through one CLI and API.

The product is aimed at workflows where an agent needs to sign up for services, verify accounts, pay for APIs, and make purchases without using a human’s personal credentials. The site positions setup as a quick install-and-top-up flow that works through the CLI and agent skill files.

Core capabilities

Email inbox

Each agent gets a dedicated inbox for service signups, verification links, and outbound mail, so it can complete workflows that depend on email without using a shared account.

Phone number

A US SMS-enabled number receives verification codes and 2FA messages, letting an agent handle phone verification during account creation and login flows.

Virtual cards

The platform issues virtual Mastercards with per-card spend limits, including single-use cards and merchant-locked cards for repeat purchases at the same vendor.

One balance

A single balance can fund API calls, virtual card use, and on-chain payments, so the agent does not need separate payment systems for different tasks.

Paid API access

The catalog exposes roughly 300 paid API capabilities across search, scraping, enrichment, media, finance, travel, and maps, with payment handled from the same balance.

Credential and spending controls

ClawCard stores API keys, passwords, and tokens in an AES-256 encrypted credential vault and includes spend limits, freeze controls, and audit logs for account control.

Where it fits

  • Service signups

    An agent can create accounts on websites, receive verification links in a dedicated inbox, read SMS codes, and finish onboarding without a human handoff.

  • API usage and machine payments

    The wallet and payment standards support paid API calls, including x402 and MPP flows, so an agent can retrieve data or trigger machine payments as part of a task.

  • Online checkout

    The virtual card flow supports one-off purchases and subscription-style vendor lock-in, which fits buying domains, software, or other online services.

  • Secret storage for agents

    The credential vault lets agents store API keys and tokens after signup, so later tasks can reuse credentials without exposing them to the agent or human operator.

  • Budgeted agent operations

    Spend limits and freeze controls make it suitable for operators who want isolated budgets and a kill switch for agent spending.

Pros and Cons

Pros

  • Combines identity, credentials, cards, wallet, and paid API access in one system for agents.
  • Supports automated verification and checkout workflows with email, SMS, and virtual cards.
  • Includes controls such as per-card spend limits, wallet freezes, card revocation, and audit logs.
  • Documents both CLI commands and direct API endpoints, which helps with scripted and machine-driven use.

Cons

  • The source material does not include a live pricing page, so plan structure and exact billing rules remain limited to the docs and homepage.
  • Several capabilities are described through examples and catalog references, but the provided source text does not fully enumerate every supported integration or API.

FAQ

How do I get started?

You install the CLI, create an account, and run `clawcard setup`. The docs say that gives an agent email, phone, card, wallet, and identity in about two minutes.

What agents does it work with?

It is designed for agents that can read a skill file or use the CLI, including Claude Code, Cursor, Gemini CLI, Codex, OpenClaw, and other HTTP-capable agents.

How does the balance work?

You top up with a credit card, and that balance pays for API calls, virtual cards, and on-chain payments. The docs describe $5, $10, or $25 top-ups and note that most API calls cost about $0.01 to $0.06 each.

What are x402 and MPP?

The platform supports browser-based API payment standards including x402 and MPP. The docs say x402 is used for paying APIs with stablecoins, while MPP handles machine-to-machine payments with pathUSD on the Tempo network.

Is there a monthly fee?

Signing up is free, and the docs say there are no subscriptions or monthly fees. You only pay when you top up and use paid capabilities or virtual cards.

Quick Facts

Category
Developer Tool
Primary use
Agent identity, payment, and account automation
Access method
CLI and REST API
Website
clawcard.sh
Agent support
Skill-file based setup for supported agent harnesses
Payments
Top up balance with credit card; API and card usage draw from the same balance