gotoHuman vs Restate

gotoHuman

Built for agent review, with TypeScript and Python SDKs, a 3-tool MCP server, an n8n node and a Make app. No status page, published rate limits or documented error responses.

Restate

An awakeable pauses a handler at no compute cost and resumes it from one HTTP request, with a durable timeout, on a free plan of 100,000 actions a month. Restate sends nothing to the approver, so the Slack message, email or inbox is the builder's code, and the published terms and privacy statement predate the paid plans.

gotoHuman

1. Call get-form-schema before request-human-review-with-form, since the field data must match the review type
2. Send agentId on every API request, because the API reference marks it required even though the JS SDK doesn't
3. Pass a webhookUrl per request when the review type has no default, or the answer has nowhere to go
4. Deduplicate webhook calls on the Idempotency-Key header, since delivery is at least once
5. Set your own deadline on the agent side and treat silence as a rejection

Restate

1. Create the awakeable, send its ID inside ctx.run, then await the promise, so a retry doesn't send a second approval request
2. Resolve with POST /restate/awakeables/<id>/resolve and a JSON body, or /reject with a text reason, which throws a terminal error in the handler
3. On Restate Cloud send Authorization: Bearer key_... to https://<env_id>.env.<region>.restate.cloud:8080. On a self-hosted server put an authenticating proxy in front of port 8080
4. Wrap the wait in orTimeout and decide what a timeout means. Without it the handler waits with no limit
5. Retry ingress errors only on 408, 425, 429 or 5xx, and only when x-restate-error-source isn't invocation