OpenDexter Access Modes
OpenDexter stays coherent across hosted connectors, authenticated account-linked flows, local packages, and agent-specific plugins by keeping the discovery and payment model consistent while changing transport and wallet semantics.
OpenDexter is available in multiple forms because different agent environments have different constraints.
The key rule is:
- same discovery story
- different wallet and transport models
Canonical Matrix
| Surface | Endpoint / Install | Transport | Wallet Model | Best For | Notes |
|---|---|---|---|---|---|
OpenDexter MCP | https://open.dexter.cash/mcp | Hosted MCP over HTTPS | Ephemeral session wallets | ChatGPT, Claude, other hosted agents | Public, no-auth, clean x402-only surface |
Authenticated Dexter MCP | https://dexter.cash/mcp or https://mcp.dexter.cash/mcp | Hosted MCP over HTTPS | Managed authenticated wallet | Signed-in users and richer account-linked flows | Can be narrowed to the clean x402 surface with the OpenDexter launch profile |
@dexterai/opendexter | npx @dexterai/opendexter install | Local stdio MCP | Persistent local wallet file | Cursor, Codex, Claude Code, local CLI agents | Best local-wallet story; optimized around the local Solana signer path |
@dexterai/clawdexter | openclaw plugins install @dexterai/clawdexter | OpenClaw plugin | Local OpenClaw wallet config | OpenClaw agents | OpenClaw-native variant of the same x402 flow |
Canonical Tool Story
All launch-facing surfaces should center the same five-tool mental model:
| Tool | Purpose |
|---|---|
x402_search | Discover paid APIs and agent resources |
x402_check | Inspect payment terms and pricing before spending |
x402_fetch | Pay and call the resource end-to-end |
x402_pay | Explicit pay-and-call alias for clients that want the payment verb visible |
x402_wallet | Inspect or fund the wallet/session path |
How To Position Each Surface
OpenDexter MCP
The public, no-auth x402 discovery gateway.
Use this when:
- the user cannot install a package
- the client supports MCP but runs remotely
- session wallets are acceptable
Authenticated Dexter MCP
The account-aware x402 surface.
Use this when:
- the user is signed in
- you want a managed wallet
- you want identity-linked x402 activity
For a launch-clean x402 story, run the authenticated server in the opendexter profile so the public claim stays focused on search, pricing, wallet context, and payment.
@dexterai/opendexter
The local package.
Use this when:
- the user wants local control of signing
- the environment supports package installation
- a persistent wallet file is preferable to a hosted session
@dexterai/clawdexter
The OpenClaw-native variant.
Use this when:
- the user is already committed to OpenClaw
- they want the x402 flow inside that agent host
- they are comfortable configuring local wallet keys in OpenClaw
Launch Guidance
When talking publicly, the cleanest summary is:
OpenDexter is the x402 search and discovery layer, available as a public hosted MCP, an authenticated managed-wallet MCP, a local npm package, and an OpenClaw-native plugin.