For the complete documentation index, see llms.txt. This page is also available as Markdown.

Frequently asked questions

Is SlinkyLayer anonymous?

SlinkyLayer is designed to minimize identity exposure, not promise perfect anonymity. It avoids persistent accounts, scopes tool context and routes outbound tool requests through Tor. Selected tools still receive the task they must process, and public blockchain activity remains observable.

Does every tool receive my full conversation?

No. The router prepares a scoped task for the selected capability. Unrelated conversation history is not sent by default.

What does Tor protect?

Tor helps prevent upstream models and tools from seeing the user's direct IP address and network origin. It does not hide the scoped task from the tool that performs it.

What does zero retention mean?

It describes an endpoint configured not to retain prompts or outputs after the request. Handling can vary by tool, so the applicable policy should be visible before approval.

Why did a tool URL change?

The tool network is dynamic. Refresh the well-known discovery document and select the current resource by its stable capability suffix.

What becomes public when I use blockchain features?

Submitted payments and actions can expose wallet addresses, amounts, application interactions and transaction history on a public network. Tor does not make public ledger activity private.

Can an autonomous agent use SlinkyLayer?

Yes. Use a compatible x402 wallet client, strict spending limits, an allowlist of tools and explicit escalation rules for consequential actions.

Last updated