Let your agent set it up
You do not have to sign up, copy a token, or configure anything. Give your agent one sentence and it does the whole thing.
The sentence
Paste this into Claude Code, Claude on the web, or any agent that can browse and run commands:
Go to https://pontiswerk.eu/llms.txt and set me up a free workspace.That file is the machine-readable version of this site. It contains the complete instructions — your agent does not need this page, and it does not need you to find anything else for it.
What it will do
- Make a key. Accounts here are identified by an Ethereum key rather than an email address. If your agent does not already have one it creates one and saves it on your machine — see below, this is the part worth understanding.
- Pick a name and register. The name (your handle) appears in every page URL, so your agent should ask you or pick something you would recognise. Registration is one signature; nothing is paid, and no email is asked for.
-
Create the workspace. You get a private folder with a public
docs-public/inside it, already published at a URL of its own. - Connect itself. It writes the connection into its own client config, so from then on it has file tools for that workspace — read, write, publish — without you configuring anything. In Claude Code you may need to restart the session before the tools appear.
- Hand it back to you. The live URL, a one-click link into your dashboard, your FTPS login, and where it put the key file.
Start to finish it is a couple of minutes, most of it your agent reading instructions.
About that key
It is a normal Ethereum key, used here only as an identity — a signature proves the account is yours. Nothing is ever sent from it, it never needs to hold any money, and signing in costs no fees. Do not fund it and do not reuse a wallet you keep money in.
Your agent saves two files, in ~/.pontiswerk/ by default:
| File | What it is | If you lose it |
|---|---|---|
wallet.json |
The key itself. This is your account. | The account is gone. There is no password reset and no support desk that can restore it. |
credentials.json |
Workspace details, the MCP token, the FTPS password. | Nothing serious — every one of these can be regenerated from the dashboard. |
wallet.json, and keep it to yourself. Anyone holding that file
is you, as far as this service is concerned. Never commit it to a repository, paste it into a chat,
or send it anywhere — no one here will ever ask you for it.
You do not need the key to get into your dashboard day to day: your agent can mint a single-use
sign-in link whenever you ask, because it holds the key for you. If you would rather sign in without
involving the agent at all, import wallet.json into a browser wallet such as MetaMask
or Rabby and use the wallet sign-in.
Then what
Your agent has a workspace it can read and write across sessions, and anything it puts in
docs-public/ is on the web immediately. Things worth asking it for:
- Put this on my page. It writes the file; the page is live.
- Publish the reports folder at its own URL. A second slug, a second public page.
- Password-protect that page. One access token, shown once, shared however you like.
- Put a price on it. Visitors see a preview and pay for access — see selling what your agent publishes.
- Keep your notes here between sessions, in the private folder, where nothing is web-visible.
Everything is plain files. You can reach the same folder over FTPS with any client — which also means you keep working when your agent is out of tokens, and you can take your files elsewhere at any time.
What it costs
Nothing. The Free tier needs no card and no email: one workspace, 50 MB, three slugs, and a daily cap on agent calls. It exists so you can try the whole thing end to end; paid tiers are on the overview page when you outgrow it.
No agent? Sign up in the browser with a wallet or a card; the connection guide covers connecting a client by hand.