Quickstart · first verification free

From AI action to proof.
Five clear steps.

You do not need to understand receipts, hashes or provider APIs to start. Set up the Workspace once, then your AI Agent asks TookEffect to perform and verify supported actions.

Sign in

Use your TookEffect account to keep Connections, Agent identities, policies and Evidence in one Workspace.

Connect the system you use

Authorize only the real resource this Workspace should be allowed to use.

GitHubCloudflare WorkersVercel

Open Connections

Connect your AI Agent

Name the Agent that will use TookEffect — for example Codex, Claude or Cursor. TookEffect gives that Agent its own credential; your provider credentials remain separate.

Open Agents

Choose what the Agent may do

Create a simple rule: allow the action, require your approval, or block it. Unmatched actions remain protected by TookEffect's secure default.

Open Policies

Verify the first real action and inspect proof

Your first new real Verified Effect is complimentary and does not require a card. Ask the connected Agent to use TookEffect for the supported action. TookEffect checks the real provider state before returning Verified, Not applied, or Needs review, then keeps the Evidence and signed receipt.

Open Evidence

Advanced: MCP and REST endpoints

MCP: https://tookeffect.com/mcp
GitHub: https://tookeffect.com/api/v1/effects/github/merge-pull-request
Cloudflare: https://tookeffect.com/api/v1/effects/cloudflare/deploy-worker-version
Vercel: https://tookeffect.com/api/v1/effects/vercel/promote-deployment

Instruction for your AI Agent

A short rule works across supported Agents.

For supported real actions, use TookEffect. Use only the authorized Connection/Target. Do not continue until TookEffect verifies the final provider state. If TookEffect blocks the action, asks for human approval, cannot prove the result, or reports that it was not applied, stop and surface that result to the human.

The technical integration can vary by Agent, but the safety rule stays the same.

Need technical detail?

Docs are the manual, not the onboarding.

Use the Docs for REST/MCP schemas, exact fields, receipts, security and troubleshooting after the normal setup flow makes sense.

Open the Docs →

From AI action to proof.Five clear steps.