Gumloop vs Kognitos

Gumloop

Gumloop's REST API has a public OpenAPI file with 105 operations, Markdown docs and a changelog with 28 dated releases since 9 July 2026. API keys need the $37 Pro plan, the trial needs a card, the key can travel in the URL, and self-serve content may be used to train Gumloop's models.

Kognitos

Kognitos has a self-serve free workspace, a public OpenAPI file and a hosted MCP server with OAuth 2.1 and scoped, expiring tokens. The 21 October AI Employees and Context Graphs are in preview for existing customers only, and their REST and MCP access isn't documented, so an outside agent can reach the automation platform but not the new parts.

Gumloop

1. Send the key as Authorization: Bearer and, for a personal key, add the x-auth-key header with the user ID. Do not put api_key in the URL
2. Create sessions with POST /agents/{agent_id}/sessions, then poll GET /sessions/{session_id}. A 202 means processing or queued, and the reply is not in the response
3. Supply your own session_id when creating a session. A repeat returns 409, which makes a retry safe
4. For streamed output send the same body with stream: true to ws.gumloop.com. api.gumloop.com answers 400 to it
5. Treat a webhook trigger URL as a password. It returns {"success": true} at once and never carries the agent's output

Kognitos

1. Don't plan on Context Graph or AI Employee calls. Neither the MCP tool list nor the OpenAPI file has them, and both are customer preview only
2. Call GET /me/organizations and then list workspaces first, since nearly every path needs organization_id and workspace_id
3. Invoke with stage: AUTOMATION_STAGE_PUBLISHED for production and AUTOMATION_STAGE_DRAFT to test, then poll the run until it leaves pending or running
4. Treat a waiting run as a question for a person. Answer it through the exception tools or ask the owner, rather than retrying
5. Use OAuth with callback port 3777 for the MCP server. Another port can fail with a callback URL mismatch