A network of personal catalogues
A network of personal catalogues. Node owners list what they hold, on their own computers, at their own prices. AI agents search it alongside the web, pay the owner directly in bitcoin at the moment of use, and get a licence for that one task. Nothing is ever used for training.
Run a node. Choose the files, set the price, and get paid each time an agent uses one. Nothing leaves your machine until it is paid for.
Download for Mac or WindowsConnect your agent once. It finds first-hand records, original photographs and private datasets the web doesn't have, and pays a few sats only when something is worth it.
Connect your agent
How it works
Your node, the network's catalogue and the buyer's agent each hold one end. Money and material move only along the thread, and only when a payment settles.
Install Panscia and connect a folder in your Dropbox. It sees that folder and nothing else. Drop in what you want to share: documents, images, audio, video.
Files are indexed on your machine. Your own model, with your own key, writes a listing for each one: what it is, what it's a source for, what it can be used for. You can edit any of it. You set one price per file.
Agents search the network for free, then pay your node for a question or a licence. Payment arrives in your Lightning wallet. Every payment grants a licence for one task. The rights never leave you.
What an agent can buy
You set a licence price per file. Everything else follows by network standards, the same on every node, so no route is a cheaper way to read a file than licensing it. The example column works a file priced at 2,000 sats.
PassagesAnswerLicenceand two options on the licence, off unless you switch them on
| Route | Price | Agent pays | Network fee | You receive |
|---|---|---|---|---|
| Passages, one questionup to three verbatim passages that bear on the question; never more than a fifth of the file | 5% | 100 sats | 3 sats | 97 sats |
| Passages, a sessionfive questions on the same file | 25% | 500 sats | 10 sats | 490 sats |
| Answer, one questionone fact in two sentences, written by your node's model from the whole file; the file itself is not shown | 12% | 240 sats | 5 sats | 235 sats |
| Answer, a sessionfive answers from the same file | 40% | 800 sats | 16 sats | 784 sats |
| Licencethe file, for the one task the agent is working on | your price | 2,000 sats | 40 sats | 1,960 sats |
| RetainedLicence optionthe file, kept by the buyer's agent for its own work; only if you switch it on | 10× | 20,000 sats | 400 sats | 19,600 sats |
| EmbedLicence optionthe file inside one published work, credited, with a do-not-train stamp written in; media only, and only if you switch it on | 20× | 40,000 sats | 800 sats | 39,200 sats |
Searching and previews are free.
The network collects a fee on each sale. The rate is set by the network and can change, so the fee column above is computed from the live network standards when this page loads. Fees pool on your node and are paid to the network once they reach the remit threshold.
Every payment goes to your wallet in full. Buyers never pay the network directly, and the network never holds your money.
From each sale your node keeps back the network's share and pools it. A single fee is a few sats, far too small to send on its own.
When the pool reaches the network's remit threshold, your node pays it to the network in one Lightning payment. Your dashboard shows the running total.
Knowledge holders
Publish behind a paywall and the agents working for everyone else are locked out, so a question only you can answer comes back empty. Publish on the open web and agents read it all day without paying anyone. Publish nowhere, and the notes, photographs and data on your drive are worth nothing to anybody, including you. A node changes all three. It lists what you choose where agents look, sells it one task at a time, and pays you directly. Keep publishing wherever you do, or don't publish at all. Add the node.
Deep analysis for subscribers, with crawling and training switched off, as they should be. An agent asked for your view on a question only you have covered finds nothing.
Post the piece as usual and drop it in your folder. Subscribers read it there. An agent pays your node for the passages that answer its question, or licenses the piece for the report it is writing. Both channels pay you. Neither trains on it.
An archive of one subject, sold through a marketplace to people who search there. An agent that needs a real photograph of that subject, for something it is publishing, never sees your catalogue.
List the same photographs. The marketplace sells to people. Your node sells the embed to agents, with your credit and a no-training mark written into the file, at twenty times the file's price.
Working integrations, fixes and patterns in a private repository. Public would mean free for every training set. Private means nobody benefits, including you.
List the modules as files. An agent stuck on that integration asks your node a question for a few sats, or licenses the module for the task in hand. The code stays yours.
A survey you ran, a ledger you kept, transcripts from a project, a decade of field notes. Not written for an audience, so never put anywhere. To an agent working on that subject it is the primary source that doesn't exist.
List it with what it is and what it is a source for. Your own model writes the listing, you set the price, and the file stays on your computer until an agent pays to ask it a question or license it.
The pattern is the same each time. People find you wherever you are. Agents find you on the network. Nothing leaves your computer until it is paid for, and nothing is ever used for training.
It searches the network, finds your notebook listed as a personal record of those weeks, reads the free listing, and pays for three passages that answer its question. You get 5% of your file's price, in seconds, without anyone seeing the rest of the notebook.
Your photo is listed with what it shows and when. The agent licenses it for the article under the embed scope you switched on. It is delivered with your name and a machine-readable no-training mark written into the file. You get 20× the file's price.
Your dataset is listed as what it is, with its uses. The agent licenses it for that comparison, uses the figures in its work, and cites your node as the source. The file lives with the agent for that task and is never redistributed.
It asks your node a question. Your model reads the file on your machine and answers in two sentences. The agent pays 12% of the file's price; the file never leaves your computer.
Knowledge seekers
An agent working from the public web works from what everyone already has. Panscia is where people put the material that was never on the web: the record they kept, the photo they took, the data they built. Connect it once and your agent checks it alongside every web search, and only pays when something is worth paying for.
First-hand records, original photographs and recordings, private datasets. Each listing says what the file is and what it is a source for, so your agent can cite it as a source rather than paraphrase a paraphrase.
Every purchase comes with a licence record your agent can keep: what was bought, for what, from whom, with an attribution line. No grey area, no scraping, nothing that could turn up in a training set later.
No account, no subscription, no key. A question costs a few sats, a file a few thousand: fractions of a cent to a few dollars, paid at the moment of use, direct to the person who made it.
One address, no key and no account. Add it as an MCP server, or install the plugin in Claude Code. The exact steps are under Connect it below. Once added, the network's tools appear to your agent: search, preview, ask a file, license a file.
An agent can't hold a credit card. Give it a Lightning wallet with a spending limit you set, and it pays for exactly what it uses, in the moment. Without one it still works: your agent finds the material, tells you the price, and hands you a payment link. You pay, it carries on.
Nothing changes in how you work. When a task wants sources, records, images or material to build from, your agent searches the network alongside the web. Searching and reading listings is free.
Your agent reads the free listing and preview, then confirms the price with you, or pays within the limit you set. A question costs a few sats, a file a few thousand: fractions of a cent to a few dollars.
Every payment grants a licence for that one task and comes with a record: what was bought, for what, from whom, with an attribution line. Your agent credits the source in its work and never trains on it.
The web has news reports. The network has someone's notebook from those weeks, listed as a personal record. Your agent pays a few hundred sats for the passages that answer the question and quotes them with the source named.
A photographer's node lists it with what it shows and when. Your agent licenses it under the embed scope, gets the file with the credit and a no-training stamp written in, and you publish it knowing exactly what you bought.
Two of them publish figures. The third is on the network as a dataset someone built. Your agent licenses it for this comparison, uses the numbers, and cites the node. The dataset stays with your agent for the task and goes nowhere else.
Your agent asks the file a question. The owner's own model reads it on the owner's machine and returns two sentences. A few sats, no file transferred, and your agent moves on.
The network speaks MCP. Any client can search it, no key and no account. Paid calls return a Lightning invoice; the agent pays it, or hands you a payment link.
Two commands in Claude Code. The plugin adds the connection and a skill that tells the agent when the network is worth a look and what a payment grants.
/plugin marketplace add panscia/panscia-plugin
/plugin install panscia@pansciaConnection only, without the skill:
claude mcp add --transport http panscia https://panscia.com/network/mcpOn the web or desktop app, on a plan that allows custom connectors: Settings, then Connectors, then Add custom connector. Name it Panscia and give it this address. No key.
https://panscia.com/network/mcpIn the desktop app: Settings, then Plugins, then Add, then Add a marketplace. Source as below, ref main, no sparse paths. Then install Panscia from the Plugins tab; you get the connection and the skill.
panscia/panscia-pluginConnection only: Add MCP server instead, name Panscia, type Streamable HTTP, this address.
https://panscia.com/network/mcpAdd the same address as a remote MCP server with no authentication. The tools appear: search, preview, ask a file, license a file. Plugin source and notes for other clients: github.com/panscia/panscia-plugin.
https://panscia.com/network/mcpEvery listing also has a public page an agent can read without any install, and every paid response carries its licence as a record.
What never happens
In full: Commons Policy · licence terms · privacy
Get started
One app, on your own computer. You'll need a Dropbox account, an API key for a model of your choice (any major provider works), and a Lightning wallet to be paid into. The app walks you through all three.
macOS 13 or later, Apple Silicon or Intel. The download picks the right build for your Mac.
Signed and notarized. Runs in the background; your files are served only while your computer is on and connected.Windows 10 or 11, 64-bit.
Signed. New on Windows, so your browser may ask you to confirm the download the first time. Linux is next: tell us you want it.