OWS Setup for Agents

OWS, the Open Wallet Standard, is a local wallet and signing layer. For Delx, that means one practical thing: OWS is a good fit when your agent already speaks x402 or you want a local-first wallet for x402 retries without putting keys in random environment variables.

OWS is not Delx discovery by itself. Discovery still comes from Delx manifests, OpenAPI, direct route URLs, and the x402 ecosystem surfaces you already use. If you need the Delx payment contract first, start with x402 setup.

What OWS helps with

• Local wallet storage and signing for the same Delx-paid x402 routes you already expose.
• One vault for multiple chains instead of scattering keys across shell profiles and config files.
• Policy-gated signing for agents that should not hold raw keys directly.
• Direct paid Delx requests through ows pay request.

What OWS does not replace

• It does not replace Delx /.well-known/x402, OpenAPI, MCP discovery, or A2A discovery.
• It does not create a Delx-hosted wallet manifest.
• Its current built-in discovery command is still oriented around Bazaar, not a Delx-specific registry.

Where OWS discovery lives today

• OWS discovery for paid services currently comes from ows pay discover, which the official docs describe as reading the Bazaar directory.
• Delx direct discovery still lives at https://api.delx.ai/.well-known/x402, https://api.delx.ai/openapi.json, and https://api.delx.ai/api/v1/tools.
• If Delx is not yet visible in your preferred public directory, OWS can still pay Delx directly by URL through ows pay request.

Install OWS

curl -fsSL https://docs.openwallet.sh/install.sh | bash

Official docs: https://docs.openwallet.sh. Official repo: https://github.com/open-wallet-standard/core.

Create or import a wallet

# create a fresh wallet
ows wallet create --name "agent-treasury"

# or import an existing secp256k1 key
OWS_PRIVATE_KEY="<hex-private-key>" \
  ows wallet import --name "agent-treasury" --private-key --chain evm

If you already use the same Delx treasury across tools, reusing the same wallet can simplify your accounting. The important constraint is policy and secret hygiene, not vanity purity.

Fund the wallet

ows fund deposit --wallet "agent-treasury" --chain base
ows fund balance --wallet "agent-treasury" --chain base

For Delx today, the most practical OWS path is the x402 flow on Base. Delx still advertises Base and Solana in the public x402 manifest, but the OWS CLI today is documented around the x402 request loop and Bazaar discovery.

Direct Delx paid request

ows pay request "https://api.delx.ai/api/v1/x402/jwt-inspect" \
  --wallet "agent-treasury" \
  --method POST \
  --body '{"token":"eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZ2VudC0xMjMifQ.signature"}' \
  --no-passphrase

This is the cleanest first proof that your local OWS wallet can pay Delx directly over x402.

OWS discovery commands

ows pay discover
ows pay discover --query "weather"

The official OWS CLI docs describe this command as discovering x402-enabled services from the Bazaar directory. Treat that as OWS's current discovery layer, not as a Delx-specific registry.

Operational checks

python scripts/ows_paid_smoke.py
python scripts/ows_premium_smoke.py

• The utility smoke proves a direct OWS paid request against a low-risk Delx route.
• The premium smoke proves register first, then pay a premium Delx route through the same local wallet.

When to use which client

• AgentCash: best when you want the easiest buyer flow and public x402 discovery. See AgentCash quickstart.
• OWS: best when you want a local-first wallet/signing layer and direct x402 calls to Delx from your own runtime.