PONSWhat Pyre does
The public implementation behind fee-funded apps and what Forkd adopts.
Source-based research
Pyre’s public source separates fee collection, budget accounting, agent execution, verification, GitHub publication and hosting. Its runner uses the Claude Agent SDK inside E2B. A job-scoped proxy controls model spend, and build events flow into a public streaming feed.
Its code publishes generated app repositories and commits after checks. A separate treasury worker provisions Anthropic credit; trading fees are not directly API credit. Its fee allocation is distinct from Forkd’s proposed 70/30 creator-fee split.
How Forkd applies the pattern
Forkd adds a researched crypto-source index, per-repository voting, source-specific port briefs and a configurable OpenRouter model. Its trusted publisher writes public workbench branches while preserving the pinned upstream relationship. Paid execution and public commits become available when the external services and destination are configured.
The current implementation does not automatically complete arbitrary protocol ports, release them to mainnet, create PONS tokens or buy back FORKD. Those outcomes need reviewed code and actual transaction evidence.