Set up an HTTP source in the RudderStack dashboard and copy the Write Key from the source configuration page.
Authenticate all requests using HTTP Basic Authentication with the Write Key as the username and an empty string as the password.
Send a track event by POSTing to {your-data-plane-url}/v1/track with a JSON body containing userId, event name, and a properties object.
Send an identify event by POSTing to {your-data-plane-url}/v1/identify with a JSON body containing userId and a traits object.
For bulk ingestion, POST an array of event objects to {your-data-plane-url}/v1/batch — the batch endpoint accepts up to 4 MB per request with individual events capped at 32 KB each.
Known gotchas
The data plane URL is your self-hosted or RudderStack Cloud endpoint — it is not a shared URL and must be configured correctly for your workspace.
Individual event payloads are capped at 32 KB; payloads exceeding this limit will be silently dropped.
The /v1/batch endpoint accepts identify, track, page, group, and screen call types — mixing unsupported call types in a batch may cause individual items to be rejected.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp