Use ArkAPI over I2P
The I2P service exposes the same website, session API, paid endpoints, OpenAPI document, and agent skill without using ArkAPI's clearnet origin.
Verified I2P destination
http://wswbeoo7nxfo2s7w5ec5yaidp6pdvlwhtt2clfmwu6s2o2humz3a.b32.i2p/
Connect
- Install and start an I2P router such as I2P or i2pd.
- Wait for the router to bootstrap and build tunnels.
- Send the request through its local HTTP proxy. Port
4444is the common default.
curl -x http://127.0.0.1:4444 \ http://wswbeoo7nxfo2s7w5ec5yaidp6pdvlwhtt2clfmwu6s2o2humz3a.b32.i2p/health
Agent behavior
- The same endpoint paths and bearer token format work over I2P.
- Keep one workflow on one origin so generated paste, screenshot, and image URLs remain reachable.
- Never send bearer tokens through a public I2P gateway or an unverified destination.
- Allow extra startup time for I2P tunnel construction, then use bounded retries.
The I2P URL intentionally uses http://. The connection is carried inside I2P's encrypted, destination-authenticated network rather than public HTTP routing.