Tool calls
Route supported HTTPS tool requests through a private relay. Keep the agent’s source IP away from the service.
Privacy infrastructure for agents
A private way to browse, call tools, and pay. Built around an attested private relay and blind-token payments.
Pay per use. No subscription.
Testnet prototype · Blind-token payments live. End-to-end VPN integration in progress.
01 / Made for the agentic web
Route supported HTTPS tool requests through a private relay. Keep the agent’s source IP away from the service.
Give web research a private network route. The destination sees the relay, while HTTPS protects request content in transit.
Pay participating services with blind tokens. The issuer verifies each token without linking it to its original top-up.
Private routing is the intended VPN flow. Sites and tool providers still receive your requests and may keep their own logs.
02 / How it works
The SDK checks the issuer’s attestation and code identity before it pays. Unexpected builds are refused.
Top up with RLUSD and receive blind-signed tokens. Your top-up is public; each token’s spending link is hidden.
Use tokens for relay bandwidth and supported paid calls. Set spending limits in code before your agent starts.
03 / Small spends. Full control.
Prepay in RLUSD. Spend tokens as your agent uses bandwidth or buys a supported service. Keep a clear balance and hard limits on every call.
04 / Privacy you can explain
The relay is designed to hide the agent’s source IP from destinations. It still sees the agent IP and destination host.
Blind signatures separate token issuance from redemption. Merchants receive valid tokens, not your top-up wallet.
The SDK checks the issuer’s attested code and keys on Google Confidential Space. Attestation verifies the workload, not what an operator may log outside it.
Websites can log requests. Logins, API keys and timing can identify an agent. Wraps does not promise total anonymity.
Built for agents. Controlled by you.