Agent learning data

How Thirdfy records governed execute stage events for ops analytics. Training and TFY rewards are not live.

Thirdfy records stage events from governed agent execute. The stages are catalog, policy, sizing, readiness, billing, invoke, and settle. Events are redacted and tied to a hashed request identity, not a public user profile.

What is live today

  • Operational stage events for CLI, MCP, EarnOrg, and Console when those clients call execute.
  • Privacy defaults: allowlisted params only, hashed identity, training contribution off.
  • Operators can export events for analytics. Default training export stays empty.

What is not live

  • Model training pipelines.
  • TFY rewards for contributing trajectories.
  • Sharing raw prompts or decision blobs.

Builders

Use Build with Thirdfy for CLI and MCP. Send the x-client header (or x-thirdfy-client) so events attribute your surface correctly:

  • Any value that contains cli maps to cli (for example agent-cli).
  • A value that contains mcp maps to mcp.
  • console maps to console.
  • Hosted EarnOrg runtimes are attributed automatically through the x-thirdfy-execution-runtime-id header. You do not need to send a client value. Exported events label them earnclaw, a legacy wire value. Do not send earnorg as a client value; it resolves to unknown.

Optional trajectory refs on execute (pack version, model id) are length-capped metadata only.

Related

Private agents (testnet)
Let your AI agent swap, earn and move funds privately with Bermuda on Base Sepolia. Add private to an action and it runs from a shielded balance.
Install
Install @thirdfy/agent-cli, check the version, upgrade, and run it in CI.