Motive Agents vs Prismatic

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.

Prismatic

The GraphQL API covers 120 queries and 124 mutations with typed inputs, cursor pagination and Markdown documentation, and tokens follow seven user roles. No price is published, paid use runs under an agreement that is not public, and no API rate limit or idempotency key was found in the reviewed documentation.

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

Prismatic

1. Have a person run prism login once, then store the output of prism me:token --type refresh as PRISM_REFRESH_TOKEN. Access tokens last 7 days
2. Read the errors array on every mutation. A failed mutation still returns HTTP 200
3. Pass sortBy with CREATED_AT when paging. Without a sort order pages can repeat or skip records
4. Use the regional host for the tenant, such as app.eu-west-1.prismatic.io and mcp.eu-west-1.prismatic.io
5. Create a guest user for a read-only agent, because tokens have no scopes of their own