Gumloop vs Motive Agents

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.

Motive Agents

Agents let Motive fleet admins turn safety, maintenance and idling events into alerts, training, work orders and in-cab calls from the Fleet Dashboard, on a platform with a 99.99 per cent dashboard SLA and audited security reports. No API, webhook or MCP tool covers Agents, so an outside agent can't create, run or read them.

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

Motive Agents

1. Don't plan to call Motive Agents. They're built and run by people in the Motive Fleet Dashboard
2. For Motive fleet data, use Motive's Public API or its MCP server instead, with the customer's admin authorisation
3. Ask the fleet's Motive admin to set up or change an Agent, and describe the trigger, condition and action you need
4. Expect Agents to place real calls to drivers and mark vehicles out of service, so confirm with the fleet manager before suggesting one