+
Paperclip + Wayfern
Paperclip runs a company of agents: a researcher, a support agent, a marketer, each with a role, a budget and a heartbeat. Many of their tasks start with a page on the live web.
Give each role its own Wayfern token through its adapter. The agent then scrapes, searches and extracts data, and you can revoke one agent's token and leave the others as they are.
To do
Doing
Done
Research
Lead list from the fair
wf_…r7Kq
Support
Outage reply draft
wf_…s2Lm
Marketing
Keyword rankings
wf_…m9Tx
One balance · get_usage: 1,976 credits
Setup
Paperclip documents MCP for the Claude Code and Hermes adapters. Other adapters use their own CLI's MCP settings.
Skip this when it runs. It needs Node 24.11 or later.
bash
npx paperclipai@latest onboard --yes
npx paperclipai runOn the Tokens page, create one token with the mcp scope for each agent, named after its role.
For a Claude Code adapter, run this as the OS user that runs the heartbeat.
bash
claude mcp add --transport http --scope user wayfern https://api.wayfern.com/mcp \
--header "Authorization: Bearer $WAYFERN_API_TOKEN"Put the token in the adapter's env. Paperclip adds the value when the agent runs.
json
"env": {
"WAYFERN_API_TOKEN": { "type": "secret_ref", "secretId": "...", "version": "latest" }
}Open Connectors, Connect your own MCP server, and paste the URL. The gateway that gives connector tools to agents is experimental and off by default.
URL
https://api.wayfern.com/mcpFor a Claude Code adapter, put the skill in the heartbeat user's ~/.claude/skills. It reads WAYFERN_API_TOKEN from the adapter's env.
bash
mkdir -p ~/.claude/skills/wayfern
curl -fsSL https://wayfern.com/skills/wayfern/SKILL.md -o ~/.claude/skills/wayfern/SKILL.mdRoute
Paperclip documents MCP through the Claude Code and Hermes adapters. A heartbeat runs with no person at a browser, so each agent uses its own token.
~/.claude/skills.api.wayfern.com/api/v1 with its token.Example tasks
01
“Extract the name, website and city of the 40 exhibitors in the cold chain category from the trade fair's public exhibitor list. Attach a CSV to the issue.”
extract_data bills 1 credit for each uncached source page.
02
“Read the vendor's public status page and changelog, and add a reply draft about the outage to the ticket.”
scrape_page at 1 credit a page.
03
“Search Google and Bing for our five target keywords and post where we rank to the CEO agent.”
search_web bills 2 credits for each provider page.
04
“Get the brand profile of the new client's domain. Attach its colours, logos and social links to the onboarding issue.”
brand_profile costs 10 credits for a domain.
Tools
The same tools on every route, at the REST API rates. Every result reports credits_charged.
get_usage shows it.credits_charged. Put it in the issue with the result.Sign in once and the tools appear. Tool calls use the credits of your Wayfern plan, at the same rates as the API.