OpenDexter CLI

Use OpenDexter from your terminal to find services, inspect a request's price, and pay through your Dexter Wallet. You need Node.js 20 or newer and a Dexter Wallet.

Install

npm install --global @dexterai/opendexter@1.23.3
opendexter --version

The second command prints the installed version.

Connect Your Wallet

opendexter connect

The terminal displays an approval link, QR code, and connection code. Open the link or scan the QR code with a device that has your passkey. On a server without a browser, use opendexter connect --no-browser and open dexter.cash/wallet/connect on another device.

Match the displayed code to your terminal and check the requesting client's name. Choose Connect with passkey and approve. Return to the terminal for the connection result. OpenDexter saves the connection on this machine for subsequent commands.

If the code expires or you cancel approval, run opendexter connect again to get a new code.

Check Wallet Access

opendexter wallet
opendexter connect status

Confirm that the wallet address matches the account you want to use. wallet shows its hosted wallet data; connect status reports payment permission, limits, remaining capacity, and expiry. Paid requests require active authority. If it is unavailable, resolve the reason shown and check again.

Manage permissions under Agents. Add money when the account needs funds.

Find a Service

opendexter search "weather API"

Select a result and read its endpoint, input requirements, supported network, and advertised price. You can also browse Indexter.

Inspect the Request

Use the endpoint you selected:

opendexter check "https://service.example/x402/route"

For a service that accepts a JSON body, include its method and documented fields:

opendexter check "https://service.example/x402/route" \
  --method POST \
  --body '{"document_url":"https://example.com/report.pdf"}'

check reads the payment terms without paying. A connected check of a paid request can return an intentId, which identifies that exact endpoint, method, and input. A POST, PUT, or DELETE check still sends a request to the provider and can change its state.

Pay for the Request

Review the returned price, asset, and network. Set a ceiling in the asset's smallest denomination. For USDC, 10000 represents $0.01 and 1000000 represents $1.

Use the returned intent ID and your chosen ceiling:

opendexter fetch \
  --intent-id "<intent-id-from-check>" \
  --max-amount-atomic "<approved-ceiling>"

fetch executes the purchase and returns the service result with payment information. Keep the intent ID unchanged. To change the endpoint or input, run check for the new request first. pay is an alias for fetch.

Recover the Result

If the response is missing or uncertain, read the status of the same request:

opendexter status --intent-id "<same-intent-id>"

A payment can complete before a response is lost. status recovers the recorded outcome without dispatching another payment. If the CLI returns noRetry, use the status command printed in its recovery output.

Open Wallet Activity to review the payment and its transaction references.

Disconnect

opendexter connect disconnect

This clears the connection saved on this machine. To remove its account access too, open Agents in Wallet, view the connected agent, and choose Disconnect. See Agents and Permissions.

Use It in an AI Client

To register the local OpenDexter MCP server in a client, name that client:

opendexter install --client codex
opendexter doctor --client codex

install updates the client's registration. doctor inspects the installation and reports configuration or connection requirements. Use opendexter setup to install into detected supported clients. For hosted connections and other client options, use Connect Your Agent.

More Commands

opendexter --help
opendexter fetch --help

Hosted spending limits come from the Wallet's approved permissions. The legacy settings command edits local settings and has no effect on those limits. Use connect status to read the permission applying to your requests.