Thirdfy V2: Governance layer for autonomous capital

Thirdfy documentation and execution now center on CLI, MCP, integrations, and EarnClaw as hosted workspace partner. V1 protocol posts are archived.

Thirdfy Team

June 2026

Autonomous agents will run a large share of consumer finance by 2030. Thirdfy exists so those agents can discover venues, pass policy checks, and execute with an auditable trail before any wallet signs.

This post explains what changed in our public docs and product story, and where to start if you integrate today.

What V2 means on docs.thirdfy.com

V1 documentation focused on ve(3,3) gauge voting, xTFY staking walkthroughs, and protocol farming. That material is retired from the public site. It lives in the repository archive for internal reference only.

The live documentation is built for integrators and operators:

Goal	Start here
Ship an agent with CLI or MCP	Quick start
Named venue coverage	Integrations
Delegation and wallet policy	Delegation and protection
TFY V2 economics	TFY token (V2)
Hosted templates and runtimes	EarnClaw docs

EarnClaw partnership

EarnClaw is Thirdfy's hosted workspace partner under a partnership agreement. You design and monitor agents in EarnClaw. Thirdfy validates intents, credits, and catalog-backed execution on the venues we integrate.

Trading, yield, and prediction templates on EarnClaw call the same action catalog documented under Integrations. Hyperliquid, Kyber, Morpho, Aegis, Polymarket, Vaults.fyi, and the rest have dedicated venue pages.

What we learned from V1 operations

Jeff's first live protocol operations in late 2025 proved that an AI operator could reduce manual runbook work dramatically. That experiment also surfaced what production agents need next: strict mandates, preflight guardrails, and repeatable schedules instead of one-off prompts.

Those lessons inform EarnClaw runtimes and Thirdfy execute-intent policy. They are not a reason to keep V1 farming docs on the public surface.