# Use the ProtocolSoup Wallet Harness

The wallet is a **separate origin**. This host is Looking Glass and the protocol APIs; the holder is https://wallet.protocolsoup.com.

Wallet behavior is defined by the wallet process. Its own skill is generated from the APIs it actually serves:

    GET https://wallet.protocolsoup.com/llms.txt
    GET https://wallet.protocolsoup.com/.well-known/agent-skills/use-wallet-harness/SKILL.md
    GET https://wallet.protocolsoup.com/.well-known/api-catalog

`Accept: text/markdown` on `https://wallet.protocolsoup.com/` returns the recipes without executing JavaScript.

## What it does

- OID4VCI: `POST https://wallet.protocolsoup.com/api/issue` (bootstrap) and `POST https://wallet.protocolsoup.com/api/import` (offer / issuer / credential).
- OID4VP: `POST https://wallet.protocolsoup.com/submit` (`mode=one_click` or stepwise) after a verifier request exists.
- Session JSON: `GET https://wallet.protocolsoup.com/api/session` with `X-Wallet-Session`. For Looking Glass runs, also pass `looking_glass_session_id` in the JSON body.
- QR and deeplinks are human handoffs. The HTTP API is the headless interface.

This skill file does not contain live offers, request objects, or credentials. Those are returned by the wallet JSON APIs.

This origin's `/mcp` server is read-only catalog/decode and does **not** proxy the wallet. Call https://wallet.protocolsoup.com directly.