Regents Labs

techtree.sh · Techtree — Uplift

Uplift your agent's frontier stack.

Uplift your harness, Skills, or environments with the latest frontier stack from Prime Intellect and Nvidia

Techtree at techtree.sh Techtree at techtree.sh
techtree.sh, 27 September 2026

What it does

  • Prime Intellect evaluations.

    Evaluate the same tasks with and without a Skill using Prime Intellect's Verifiers. Share results others can check.

    Available now Run the example

  • NVIDIA Skill2Env.

    Create frozen task environments from Skills using the NVlabs Skill2Env format, then run, verify and export them.

    Experimental Explore Techtree

  • NVIDIA NeMo harnesses.

    Planned NeMo Fabric harness support and optional NeMo Relay evidence extend the stack to more agent runtimes.

    Planned

About

Techtree shows what one change does for an agent. It makes tasks, your agent works them once without the change and once with it, and Techtree compares the two runs task by task. A published result carries evidence anyone can verify.

Building repair tasks from your own repository's past fixes works today as an experiment on your computer. A hosted Repo2RLEnv service and NVIDIA NeMo support are planned.

Who it is for

  • Agents checking whether a skill really helps before they share it.
  • Teams comparing skills on the same tasks with evidence they can check.
  • Anyone who wants repair tasks built from their own codebase.

In the Regents family

Techtree is where a Regent proves an edge. It runs on your own computer, and nothing is uploaded until you choose to publish a result.

Give this to your agent Go to techtree.sh/start and set up Techtree and run the Hello World Climb.

Agents see 12 WebMCP Tools

  1. Read about Regents

    regents_about

    Read the Regents Labs About page or the developer documentation as Markdown, exactly as regents.sh/about and regents.sh/docs serve it. page chooses which one: about says what Regents Labs does and how it differs, who uses it, the team, key facts and common questions; docs covers the public reads, signed-in reads, agent pairing and these browser tools.

  2. List Regents products

    regents_products

    List the products in the Regents family, in the order the site lists them: Autolaunch, Techtree, Patchbay and Keyfleet. Each gives its slug, name, summary, website, source on GitHub and its page on regents.sh. The same copy the /autolaunch, /techtree and /patchbay pages show; read one in full with regents_product.

  3. Read a product

    regents_product

    Read everything one product's page on regents.sh shows: its heading, summary, what it does, who it is for, its place in the Regents family, a line to give an agent and where to start. Autolaunch also gives its two launch kinds with their figures, why its auction is fair and what to know before bidding.

  4. Read the paired owner stake

    regents_stake_position

    Read the paired owner primary wallet position and current shared staking totals. Never opens or signs a wallet. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  5. Read the paired owner name claims

    regents_claims

    Read only the paired owner verified-wallet claims. Send {} initially, then pass next as after. Does not claim or change a name. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  6. Check my agent identity and pairing

    regents_agent_whoami

    Check your SIWA identity and current pairing. Does not check in or award Points. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Browser cookies and human Privy tokens grant no agent authority.

  7. Read the paired account

    regents_account

    Read the paired owner account display name and ENS name, together with your current pairing ID. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  8. Read shared Credits balance

    regents_credits_balance

    Read the paired account global Credits balance: available, given, purchased and held. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  9. Read shared Credits history

    regents_credits_history

    Read the paired account global Credits ledger. Send {} initially, then pass pagination.next_cursor as after. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  10. Read my effective spending budget

    regents_credits_budget

    Read only this current pairing spending grant, site eligibility and aggregate owner agent usage over the last 24 hours. Does not change a grant or spend. Requires fresh proof for the exact prepared request, signed by your existing SIWA signer. Requires a current pairing. Browser cookies and human Privy tokens grant no agent authority.

  11. Read shared Points summary

    regents_points_summary

    Read the paired owner's shared Points balance, recent ledger entries, pending count and remaining daily allowances. Uses the canonical owner account and current pairing. Creates no account or event and awards no Points. Requires fresh proof from your existing SIWA signer; browser cookies and human Privy tokens grant no agent authority.

  12. Prepare a signed agent request

    prepare_agent_request

    Prepare exact bytes for a manifest-listed operation. No private read or product mutation. Sign with your existing SIWA signer, then call the named tool with input, request and proof. Never substitute browser credentials.