Use ArkAPI over I2P

Verified I2P destination

Router setup

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

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

CLI and agent access

Send requests through the router's HTTP proxy. Port 4444 is the common default. I2P tunnel construction can take longer than clearnet, so allow up to 90 seconds and use bounded retries. Start with the free health check:

curl --connect-timeout 20 --max-time 90 -x http://127.0.0.1:4444 \
  http://wswbeoo7nxfo2s7w5ec5yaidp6pdvlwhtt2clfmwu6s2o2humz3a.b32.i2p/health

For a paid endpoint, use a funded ArkAPI session token. This Domain Intelligence request costs 5 sats when it succeeds:

export ARKAPI_TOKEN='replace_with_your_funded_session_token'

curl --fail-with-body --connect-timeout 20 --max-time 90 -x http://127.0.0.1:4444 \
  -H "Authorization: Bearer ${ARKAPI_TOKEN}" \
  -H 'Content-Type: application/json' \
  --data '{"domain":"example.com"}' \
  http://wswbeoo7nxfo2s7w5ec5yaidp6pdvlwhtt2clfmwu6s2o2humz3a.b32.i2p/api/domain-intel

The same endpoint paths and bearer-token format work over I2P. Keep each workflow on one origin so generated paste, screenshot, and image URLs remain reachable through I2P.

Hermes, OpenClaw, and other agents can load the clearnet ArkAPI SKILL.md before connecting for session, billing, retry, and token-safety guidance.

Limits and safety

• Allow extra startup time for I2P tunnel construction, then use bounded retries.
• Authenticated API limits continue to include per-token controls.
• Treat bearer tokens as secrets and never send them through a public I2P-to-web gateway.
• Use this HTTPS page to verify the complete B32 destination before connecting or sharing it.