Fund an OpenClaw test wallet

Before you start

You need a working OpenClaw installation, access to the chosen agent’s workspace, an HTTP-capable tool such as curl, and a separate Bitcoin Signet receiving wallet. Installing this skill does not create a wallet or grant additional tool permissions.

Use a fresh Ark address from Bark connected to https://ark.signet.2nd.dev/, a Signet Lightning invoice, or a Signet on-chain address. Start with the agent API guide for supported destinations and current wallet requirements.

1. Add the skill to your OpenClaw workspace

In a terminal, change to the workspace configured for the agent you want to use. Download the skill for review, then save it as skills/ark-faucet/SKILL.md inside that workspace. If a skill already exists at that path, review the changes before replacing it.

curl --fail --silent --show-error \
  https://arkfaucet.com/skills/ark-faucet/SKILL.md

After reviewing it, save the skill from the root of that agent’s workspace:

mkdir -p skills/ark-faucet
curl --fail --silent --show-error \
  https://arkfaucet.com/skills/ark-faucet/SKILL.md \
  --output skills/ark-faucet/SKILL.md

OpenClaw discovers workspace skills under <workspace>/skills. The frontmatter name is ark-faucet. Start a new agent session after adding it. These steps follow the OpenClaw skill loading documentation.

2. Confirm that the agent can read the API

Ask OpenClaw:

Load the ark-faucet skill. Check https://arkfaucet.com/api/status and report the network, allowed amounts, supported rails, and remaining daily sats. Do not request a payout yet.

If the skill is missing, confirm that you used this agent’s actual workspace and that its skill allowlist includes ark-faucet. If HTTP access is unavailable, enable an appropriate tool through your usual OpenClaw configuration; the skill alone cannot make network requests.

3. Request one test payment

For an Ark test, generate a fresh receiving address in your compatible Signet wallet. Replace the placeholder below with that complete address:

Use ark-faucet to request 500 Signet sats over Ark to tark1YOUR_FRESH_ADDRESS. Check availability first. Submit once and report the exact result. Stop on a rate limit or uncertain payout.

The agent should send this request body to POST /api/request:

{"rail":"ark","destination":"tark1YOUR_FRESH_ADDRESS","amount_sats":500}

Expect HTTP 200 with success: true and status: sent. Verify the receiving wallet before using its funds in another test. For a Lightning test, supply a fresh lntbs invoice and explicitly request the Lightning rail instead; see the invoice guide.

Using on-chain payouts in an OpenClaw workflow

Ask for on-chain explicitly and supply a fresh lowercase Signet tb1 address. HTTP 202 means queued. Have the agent retain and poll the exact claim_status_url, rather than sending another payout request.

Keep that URL out of public logs and shared messages. A sent result means broadcast; wait for the wallet’s confirmation requirement before a dependent task. Stop on failed or unknown.

Troubleshooting

• 400 or 415: read the JSON error and correct the destination, amount, rail, or content type before another request.
• wrong_ark_server: use the returned required_ark_server and generate a new compatible address.
• 429: report Retry-After or retry_after_seconds and stop. Do not rotate IPs, change transports, or swap destinations to bypass a limit.
• payout_unknown or an on-chain unknown status: stop without a replacement claim; the original payment may have been sent.
• Other 503 errors: use bounded backoff and stop after a few attempts. If a connection drops after submitting a claim, do not assume the payment failed.

Compatibility and references

The installation path and session behavior were checked against OpenClaw’s documentation on September 7, 2026. Payment examples follow ArkFaucet OpenAPI 2.1.1. Agent releases and local tool policies can differ; confirm installation in your own environment.

This is an unofficial integration guide. ArkFaucet is not affiliated with OpenClaw.

Keep building

Read the faucet skill, OpenAPI contract, or compact service documentation. Privacy transport setup: Tor and I2P.