---
name: thirdfy-condor
description: "Use Condor through Thirdfy (3 reads, 1 write): one MCP, CLI and API for every agent, with each write checked against the owner's policy before it signs."
---

# Condor through Thirdfy

Run Condor trading bots under the owner's daily caps and policy.

- Status: Live
- Chains: –
- Can touch: 1 write action from the agent's wallet, each checked against the owner's mandate before it signs.
- Directory: https://v2.thirdfy.com/protocols/condor

## Connect

- MCP: `claude mcp add --transport http thirdfy https://mcp.thirdfy.com/mcp` (docs: https://docs.thirdfy.com/documentation/mcp)
- CLI: `npx @thirdfy/agent-cli@latest login` (add `--trade` to allow writes), then `npx @thirdfy/agent-cli@latest whoami`
- The owner allows Condor for the agent: https://v2.thirdfy.com/integrations/condor

## Actions

- `condor-executor-stop` (write): Stop a Condor-managed Hummingbot executor (no new day-cap reservation).
- `condor-executor-create` (read): Reserve Condor Pattern A day notional and return a reservation id for governed HB create.
- `condor-reservation-release` (read): Release a Pattern A reservation (EarnClaw prepaid fail-closed after allow).
- `get-condor-policy-status` (read): Read Condor Pattern A UTC-day cap and reservation status for a runtime.

## Rules

- Call these actions through Thirdfy, not with your own keys: Thirdfy builds each transaction and the owner's policy checks it before it signs.
- A write that the owner has not allowed, or that breaks a limit, is refused before signing and costs nothing.