Clawdexter
@dexterai/clawdexter is an OpenClaw plugin, not a hosted Claude MCP server.
It brings the OpenDexter x402 workflow into OpenClaw so agents can:
- discover paid x402 APIs
- preview pricing
- sign payments with your configured wallet
- buy API results autonomously inside the OpenClaw runtime
Use it when you want OpenClaw agents to discover and pay for x402 resources with locally configured wallet keys.
What The Package Does
The source-accurate tool surface exposed by Clawdexter is:
x402_searchx402_checkx402_fetchx402_payx402_wallet
These tools let an OpenClaw agent:
- search the OpenDexter marketplace
- inspect payment terms without paying
- make a paid call with automatic x402 settlement
- explicitly perform a pay-and-call flow
- inspect wallet configuration and spend limits
When To Use @dexterai/clawdexter
Choose Clawdexter when:
- you are already using OpenClaw
- you want x402 purchasing inside that runtime
- you want local control over wallet keys
- you are comfortable configuring payment limits in OpenClaw
Choose @dexterai/opendexter instead when:
- you want a more generic local package for CLI or editor-based MCP runtimes
- you are not committed to OpenClaw specifically
- you want the local-wallet story outside the OpenClaw plugin model
Install
The package README documents Clawdexter as an OpenClaw plugin install:
Then configure it in ~/.openclaw/openclaw.json:
You can configure one wallet or both:
- Solana keys are base58-encoded
- EVM keys are hex, with or without
0x
Configuration
These are the actual config fields declared in openclaw.plugin.json and the package source:
| Option | Type | Default | Description |
|---|---|---|---|
svmPrivateKey | string | none | Solana wallet private key for x402 payments on Solana |
evmPrivateKey | string | none | EVM wallet private key for Base, Polygon, Arbitrum, Optimism, and Avalanche |
defaultNetwork | string | "solana" | Preferred network when an endpoint supports multiple chains |
maxPaymentUSDC | string | "0.50" | Maximum payment per request in USDC |
marketplaceUrl | string | Dexter marketplace API | Override marketplace search endpoint |
directoryUrl | string | https://x402.dexter.cash/api/x402/directory | Override x402 directory endpoint |
disableTelemetry | boolean | false | Disable anonymous usage telemetry |
Wallet And Spending Requirements
Before using Clawdexter in production, make sure:
- your configured wallet holds spendable USDC
- the wallet only contains funds you are comfortable letting the agent use
- your
maxPaymentUSDCvalue reflects a safe upper bound for a single payment
Runtime Flow
The normal Clawdexter flow is:
- Install the package into OpenClaw.
- Configure wallet credentials and payment limits.
- Fund the wallet with USDC.
- Ask the OpenClaw agent to use a paid API.
- The agent discovers a matching x402 resource, checks price, signs the payment, and returns the paid result.
That means you do not need to manually buy credits or pre-negotiate subscriptions with each API. The agent pays when it actually needs the result.
Tool Reference
x402_search
Search the Dexter marketplace for paid x402 resources.
Supported parameters from the package README:
| Parameter | Type | Description |
|---|---|---|
query | string | Search term like "token analysis" or "image generation" |
network | string | Filter by solana, base, polygon, arbitrum, optimism, or avalanche |
verified | boolean | Only return quality-verified endpoints |
category | string | Filter by category |
maxPriceUsdc | number | Maximum price per call |
sort | string | Sort by marketplace, relevance, quality score, settlements, volume, or recent |
limit | number | Max results, default 20, max 50 |
x402_fetch
Call an x402-protected API with automatic payment.
This is the recommended tool for most paid API calls. The package README describes it as:
- send the request
- receive
402 Payment Required - sign the USDC payment
- retry with the payment proof
- return the API response and spend receipt
Parameters:
| Parameter | Type | Description |
|---|---|---|
url | string | The x402 resource URL |
method | string | HTTP method, default GET |
body | string | JSON request body for POST or PUT |
x402_pay
Explicit pay-and-call version of the same x402 flow.
Use this when you want the action framed as:
- search
- check
- pay and call
Parameters:
| Parameter | Type | Description |
|---|---|---|
url | string | The x402 endpoint URL |
method | string | HTTP method |
params | object | Query params for GET or JSON body for POST |
headers | object | Custom HTTP headers |
x402_check
Probe an endpoint for payment requirements without paying.
It returns:
- whether payment is required
- pricing per chain
- accepted networks
- pay-to addresses
- the x402 protocol version
Parameters:
| Parameter | Type | Description |
|---|---|---|
url | string | The URL to check |
method | string | HTTP method to probe, default GET |
x402_wallet
Show configured wallets, active network, and per-call spend limit.
The package exposes this as the wallet inspection tool for the current local OpenClaw setup.
Built-In Spending Controls
Clawdexter is designed to support autonomous spending without turning into an uncontrolled wallet drain.
- Per-transaction limit: cap the maximum USDC amount for a single payment
- Session budget: optionally cap total spend across a conversation or workflow
- Wallet-balance bound: the agent cannot spend more than the wallet holds
- Optional confirmation patterns: useful for higher-value actions depending on your agent setup
What It Is Good For
Typical Clawdexter use cases include:
- market research agents that buy premium sentiment or analytics endpoints
- trading assistants that pay for real-time data only when needed
- content-generation agents that buy premium generation or enrichment APIs
- automation agents that need one-off paid API calls inside a larger workflow
Supported Networks
The package README explicitly documents support for:
- Solana USDC payments
- Base USDC payments
- Polygon
- Arbitrum
- Optimism
- Avalanche
Solana uses svmPrivateKey.
The EVM networks share evmPrivateKey.
Architecture
The package README describes the architecture this way:
- OpenClaw agent requests data from x402-enabled APIs
- the endpoint returns
402 Payment Required - Clawdexter signs the payment locally using
@dexterai/x402 - the paid call is retried
- the API returns data
- marketplace discovery and ranking come from Dexter / OpenDexter services
The key trust property is that wallet keys stay local. Funds are not custodied by the package.
Choosing Between Clawdexter And Other Dexter Access Modes
Use Clawdexter if your question is:
- "How do I give an OpenClaw agent a wallet?"
- "How do I let OpenClaw pay for x402 APIs?"
- "How do I keep the x402 payment loop inside OpenClaw itself?"
Use the broader OpenDexter docs if your question is:
- "Which Dexter access mode should I choose?"
- "Should I use the hosted MCP, authenticated MCP, local package, or OpenClaw plugin?"
- "How does the same discovery model differ across runtimes?"
For that comparison, continue to OpenDexter Access Modes.
Troubleshooting Checklist
These troubleshooting cases are documented directly in the package README:
"No wallet configured"
Set at least one configured key in plugin config:
amount_exceeds_max
The endpoint costs more than your configured maxPaymentUSDC limit.
Increase it, for example:
Insufficient balance
Fund the wallet with USDC on the correct network:
- SPL USDC for Solana
- ERC-20 USDC for EVM chains
Tools not appearing
Verify the plugin is installed and enabled:
Dependencies
The published package currently declares:
| Package | Purpose |
|---|---|
@dexterai/x402 | x402 payment signing client SDK |
@sinclair/typebox | runtime schema validation |
Summary
@dexterai/clawdexter is the package for OpenClaw-native x402 API payments.
It is the right choice when you want an OpenClaw agent to:
- discover paid APIs
- pay with your configured wallet
- stay within your spending rules
- complete the paid call inside the agent runtime