TFBthumb  ·  Beta access

Run a real workflow.

The playground refuses every consequential intent. The beta does not, but it surfaces each one to your approver before it dispatches. You hold the lever; the agent holds the wheel.

What a beta engagement looks like

Documents that ship with your key

API reference

Endpoints, request/response shapes, run lifecycle states, ledger receipt format.

Read the API spec

What this does NOT promise

The full boundary list. Multi-tab, cross-origin iframes, GET-with-side-effects, LLM-Brain, unattended autonomy: all explicitly out of scope.

Read the limits

Evaluation agreement

One page. 30-day term. Mutual confidentiality. Acceptable-use clause. We countersign by email reply.

Read the agreement

What is verified before your first run

The bounded-claim set on the main page is what is promised. An independent third-party reviewer (Gemini) returned verified on it. Two TFB inspectors (DAVID+ and CODE_MECHANIC) confirmed the same set against the canonical SHAs. Every claim is backed by a runnable gate; every gate prints PASS on the version your key binds to.

Beta does not extend the bounded set. It gives you access to it on your own targets, with a human-in-the-loop approver for the consequential tier.

How to request a key

Send one email · evaluation is free during validation

Paid tier is coming. While the bounded-claim set is in the public-validation phase, evaluation keys are issued at no cost to the first qualifying organizations. Subject: TFBthumb beta, <your org>. Tell me what target you want to point it at and what the success condition is. I read each one personally and reply with the agreement and a key within one business day. Saul@projecttfb.com