Early trial · Self-hosted · Test tokens
Your cloud. Your wallet. Your rules. MoneySwitch gives agents across your devices separate MoneyKeys to use one wallet. Try it with your bots, then help make it better with a PR.
You currently need your own deployment; there is no public hosted-account signup. The trial uses test USDC with no real value. Bring a runtime and follow the wallet's faucet instructions to obtain test tokens. This is not a dollar-denominated API credit offer.
Build in the open · Start with a trial
A clearer setup instruction, a reproducible bug, or a smoother key creation flow can all start a contribution. Send small fixes directly; discuss larger features in an issue first.
The guide covers forking, documentation edits, verification and submission. You can also share feedback without code; GitHub submissions require an account. Rewards are discretionary, based on trials and feedback; opening a PR does not automatically earn one.
One agent is enough to start. Feedback about a failed setup is useful too.
Payments currently cover supported USDC / x402 services. This does not pay arbitrary websites or existing AI subscriptions.
A small end-to-end experiment
Follow the Docker + HTTPS deployment guide (Chinese) or the source quickstart. Isolate the service from your agents' machines or system permissions so the agents can only access it over the network with MoneyKeys.
Keep the administrator sign-in link from the first start private. Create a wallet, save its recovery phrase yourself, and use the wallet page's faucet instructions to obtain Monad testnet USDC. You do not need mainnet funds for this trial.
On the Keys page, use distinct names such as laptop-codex and cloud-claude. Select Testnet for both and keep the test payment endpoint enabled. Here is one suggested policy; all amounts are test USDC:
| Setting | Agent A | Agent B |
|---|---|---|
| Total / daily budget | 0.05 / 0.05 | 0.05 / 0.05 |
| Per-request limit | 0.02 | 0.02 |
| Approval threshold | Leave empty | 0.01 |
Give each agent its own skill paragraph and check that it can reach your HTTPS service URL. Keep the approval PIN with a person. Do not put a PIN, administrator token or recovery phrase in an agent's skill. With one agent, try the two keys one after another.
When the test endpoint is enabled, the skill instructs the agent to check its budget and make one 0.01 test USDC payment to https://app.moneyswitch.dev/x402-testnet/check. Do not repeat that payment manually.
A should pay within its limits. B reaches its approval threshold and should return an approval link first. Use that key's PIN to approve, or approve as the administrator in the dashboard; the agent then follows the skill to continue the request. Save the successful transaction hash. If you see charged: maybe or a timeout, check Bills before taking further action; do not retry automatically.
Look for each key in Bills: amount, URL, chain, charge status, and a transaction hash for a confirmed payment. Revoke A's key and ask A only to check GET /v1/status; it should be rejected. No further payment is needed.
Note the least clear step, any error, and a real service you would want an agent to buy. If you cannot get test tokens or finish deployment, report that too.
You run the service and manage the wallet and its data on your own server. Agents receive budget-limited access keys. Anyone who can read the server's wallet data and unlock file can use the wallet; protect the server and treat any future mainnet deployment as a small spending wallet.
Agents share one payer's wallet, with separate keys and limits. A key's budget is a spending ceiling, not a separately funded balance. The same wallet address has independent balances on each supported chain.
We may offer rewards at our discretion based on trial participation and feedback. Reward details and criteria will be announced separately; participation does not guarantee a reward or a fixed amount. There is no sharing or positive-review requirement, and criticism is welcome. Test tokens have no real value; your own hosting or runtime may incur costs.
Per-payment purpose notes and task-level cost reports are not implemented. Child keys have backend APIs but no creation UI. Integration is through a skill and HTTP, without MCP or a public multi-tenant hosted service.
Tell us what actually happened
Tell us which agents you used, how far you got, what you expected, what happened, and whether you would use this again. Negative feedback is welcome. We may offer discretionary rewards based on participation and feedback, with details announced separately.
GitHub Issues require a GitHub account and are public. Share redacted observations and error codes only, without keys, PINs, recovery phrases, administrator links or raw logs. Report security vulnerabilities through the private reporting channel.