I2P · Verified service

Use ArkFaucet over I2P

A normal browser cannot resolve a .b32.i2p destination. Start an I2P router and use its local HTTP proxy, then open the verified address below. The faucet form, agent API, and documentation use the same paths as clearnet.

Verified I2P destination

http://vdth7f4yn5yzh2rpgwo5m5hegx7yvvvsw46jxsi2phknzk5zacxq.b32.i2p/

Back to faucet

Connect to I2P

Install and start an I2P router such as I2P or i2pd.
Wait for the router to bootstrap and build tunnels.
Configure your browser or client to use its local HTTP proxy, commonly 127.0.0.1:4444.
Copy the complete destination above and verify it ends in zk5zacxq.b32.i2p.

The I2P URL uses http:// by design. I2P authenticates the destination and encrypts traffic inside the I2P network.

CLI and AI agents

Send requests through your router's HTTP proxy. I2P tunnel construction can take longer than clearnet, so allow up to 90 seconds and use bounded retries. Check faucet status before requesting sats.

curl --connect-timeout 20 --max-time 90 -x http://127.0.0.1:4444 \
  http://vdth7f4yn5yzh2rpgwo5m5hegx7yvvvsw46jxsi2phknzk5zacxq.b32.i2p/api/status

Hermes, OpenClaw, and other agents can load the ArkFaucet SKILL.md before using the same API paths over I2P.

Limits and safety

Ark, Lightning, and on-chain payout rails are available over the same I2P API paths.
For Ark payouts, follow Second’s Bark Signet setup guide and use a fresh tark1 address.
I2P and Tor share a five-claim rolling hourly payout limit, plus the same one-claim-per-destination, on-chain, and global rolling caps as clearnet.
The I2P service does not apply a per-IP limit because it does not receive a dependable clearnet client IP.
Keep an on-chain claim_status_url private and poll it only through the same origin.
Never use a public I2P-to-web gateway; it can observe and alter traffic.
Signet sats are valueless test funds. ArkFaucet never distributes mainnet Bitcoin.