Send an automated carrier packet invitation (Intellivite) from a broker TMS into MyCarrierPackets
domain: mycarrierpackets.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get an integration username/password from a MyCarrierPortal admin (managed under mycarrierpackets.com/IntegrationTools) and exchange them at the /token endpoint (grant_type=password) for a security token
Optionally call PreviewCarrier with the carrier's DOT/docket number to preload approved emails, risk assessment, and certificate data before inviting
Call EmailPacketInvitation with dotNumber, docketNumber, carrierEmail, and (recommended) a username so MCP can attribute the invite to the sending user
Alternatively, generate a user-specific Intellivite deep link (mycarrierpackets.com/{CustomerIntelliviteID}/Carrier/Intellivite/{MCPUserID}/{DOT}/{Docket}) and embed it in your own onboarding email instead of calling the invite API directly
Track invited carriers and poll for completed packets rather than assuming invitation success means the carrier finished onboarding
Known gotchas
There are three separate ways to send an invite (API call, deep link with user/DOT/docket, or bare deep link) with different data-prefill and attribution tradeoffs - picking the wrong one loses either efficiency or user tracking
All POST calls require a bearer token from the separate /token endpoint first - there is no combined invite-plus-auth call
Response format defaults to JSON; you must explicitly add an Accept: text/xml header to get XML, which is easy to miss if copying examples
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?