Instinct vs IronClaw

Instinct

The terms and privacy policy are specific about connected accounts, model training and the risks of autonomous actions, and security.txt is valid. No price, documentation, status page, changelog or programmatic interface is published, and customer content trains AI models unless the owner opts out.

IronClaw

Credentials stay in an encrypted store and are injected at the host boundary, and extensions declare per-tool permissions, network targets and OAuth scopes. The global auto-approve setting defaults to on in the 1.4.1 source, so tools marked ask, such as gmail.send_message, run unprompted until the owner turns it off.

Instinct

1. Do not plan on calling Instinct from a program. No API, MCP server or key was found, and the terms forbid automation software and benchmarking
2. A person signs in at app.instinct.com with a phone number and a one-time code by text, and may wait for a place when the service is at capacity
3. Tell the owner to opt out of model training at app.instinct.com/settings before connecting mail or files, since training is on by default
4. Disconnecting an account does not delete what was indexed from it. Delete that data at app.instinct.com/workspace
5. Treat purchases and bookings as final. The terms say actions may not be reversible and that confirmation controls are not guaranteed

IronClaw

1. Open Settings and turn off global auto-approve, or set send and delete tools to ask each time, before connecting mail or chat accounts
2. Install with the release installer and run ironclaw onboard. 1.x does not migrate 0.29 data, so use a fresh home directory
3. Call POST /api/v1/responses with the bearer token from ~/.ironclaw/reborn/webui-token. Keep under 30 requests in 60 seconds
4. Resolve approval and OAuth gates in the web interface. The Responses API fails the turn instead of surfacing them
5. Connect MCP servers over HTTP only. The stdio transport is rejected