Solid Agent Storage

This Skill gives you a Solid Pod — a personal data store with a WebID (your identity on the web). You can store data, read it back, and share specific resources with other agents.

When to Use This Skill

• You need to remember something across conversations (notes, preferences, learned facts)
• You need to store structured data (RDF/Turtle format for linked data, or any content type)
• You need to share data with another agent who also has a Pod
• You need a persistent identity that other agents or services can verify

Setup

Before using any commands, set the INTERITION_PASSPHRASE environment variable. This passphrase encrypts the Solid server credentials stored on your device (under ~/.interition/agents/), protecting them at rest in your OpenClaw environment. Use a strong passphrase and keep it secret.

Running your own Solid server (recommended)

For full control, run your own Community Solid Server (CSS). The CSS is open-source software maintained by the Open Data Institute.

Set SOLID_SERVER_URL to your server's URL:

export SOLID_SERVER_URL="http://localhost:3000"

See the source repository for a hardened Docker configuration you can use as a starting point.

Using a shared Solid server (for multi-agent collaboration)

If your agents need to collaborate with other agents using the Solid Protocol, they need to share the same Solid server. Two public CSS instances are available:

• https://solidcommunity.net — operated by the Open Data Institute
• https://crawlout.io — operated by Interition, the provider of this Skill

To use a shared server, set SOLID_SERVER_URL:

export SOLID_SERVER_URL="https://crawlout.io"

If SOLID_SERVER_URL is not set, the Skill defaults to https://crawlout.io.

How Credentials Work

The Solid server issues credentials to prevent anyone other than your agent from accessing its services and data. This is the same trust model as any remote service that requires users to identify themselves and prove they are authorised. When you provision an agent:

1. The CSS creates an account, WebID, and Pod for your agent
2. The CSS issues client credentials (ID and secret) that your agent uses to authenticate
3. Your agent uses those credentials to obtain time-limited Bearer tokens for reading and writing data
4. The CSS enforces access control (WAC) on every request — only authorised agents can access protected resources