Practical overview
When it fits
Consider Inktoll when designing an agent workflow that needs paid access to publisher articles and a described payment path for citations, or when assessing publisher onboarding for machine readership.
Who it is for
- Publishers seeking a way to charge automated readers for individual articles.
- Developers building AI agents that browse or use paid publisher content.
- Teams evaluating payment-linked citations for machine-consumed material.
Documented uses
- Discover articles through RSS and pay for per-article access.
- Route a citation toll when an agent uses purchased content in an answer.
- Browse the article catalog and invoke reading or question-answering tools through the documented MCP server.
- Onboard Ghost or Paragraph publications for indexing and publisher payments.
Requirements & limits
The project README describes the service as live on Arc mainnet and says creator onboarding is open. A personal Circle developer-controlled wallet is described as being provisioned on first use for an agent handle.
- Publisher integrations labeled live are Ghost and Paragraph; X is described as in progress and Substack as coming soon.
- The documented stack includes TypeScript, Circle Programmable Wallets and Gateway, x402, Arc mainnet, LangChain, OpenAI gpt-4o-mini, Next.js and SQLite.
- The MCP tool list includes free catalog browsing, paid article reading and question-answering that can trigger citation tolls.
- Local setup requires OpenAI and Circle API keys plus Arc settlement configuration.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Inktoll locally
Prepare the local backend, AI reader agent, and web dashboard using the README’s setup sequence.
Before you start
- A local copy of the Inktoll repository, with the
server,agent, anddashboarddirectories. - Node.js and npm available to install and build the project.
- An OpenAI API key and Circle API key.
- Arc mainnet configuration values and a Circle Gateway URL as listed in the README.
Steps
Create a root
.envfile from the documented template, settingPORT=3001,AGENT_PORT=3002, the API keys, and the Arc and Circle settlement values.From
server, run the command below, the command below, and the command below; the README says the server runs athttp://localhost:3001.npm installnpm run buildnpm startFrom
agent(usingcd ../agentafter the server commands), run the command below, the command below, and the command below; the README says the agent runs athttp://localhost:3002.npm installnpm run buildnpm startFrom
dashboard(usingcd ../dashboardafter the agent commands), run the command below, the command below, and the command below; the README says the dashboard is available athttp://localhost:3005.npm installnpm run buildnpm start -- -p 3005
Expected outcome
The README describes a local server, AI reader agent, and dashboard running on ports 3001, 3002, and 3005 respectively.
Guide limitations
- The README supplies configuration placeholders, not actual API credentials; do not use placeholder values as working credentials.
- The README’s local setup instructions do not establish that the payment flow has been independently tested or verified.
Start Inktoll services on a VPS with PM2
Use the documented PM2 setup to start the backend server and autonomous agent loop as background processes on a VPS.
Before you start
- A VPS with the Inktoll repository and its documented configuration in place.
- Node.js/npm and access to install PM2 globally.
- The repository’s
ecosystem.config.jsfile.
Steps
Install PM2 globally with the command below.
npm install -g pm2From the repository root, run
pm2 start ecosystem.config.js.
Expected outcome
The README says this starts the backend server and autonomous agent loop as background daemons.
Guide limitations
- The README does not specify VPS sizing, operating-system compatibility, or additional server-hardening steps.
- The documented PM2 commands do not independently verify that the services start successfully or remain online.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- mrnetwork0001/Inktoll · Official homepage title · retained in its source language

