Accept POST /Bulk requests with Content-Type application/scim+json containing {schemas: ['urn:ietf:params:scim:api:messages:2.0:BulkRequest'], Operations: [...], failOnErrors: N}
Support bulkId references: when a later operation's data references a resource created earlier in the same bulk request using a bulkId (e.g. '$ref: bulkId:user-temp'), resolve the bulkId to the actual resource location after the creating operation succeeds
Process operations in order; if an operation fails and the running error count reaches failOnErrors, stop processing and return results so far — do not roll back already-committed operations
Return a BulkResponse with a response item per input operation containing {method, location, version, status.code, response (if error)}; completed operations with no error include only method, location, version
For circular bulkId references (A references B, B references A in the same request), return a 409 or 400 error for those operations — do not attempt to resolve the circular dependency
Advertise bulk support in the SCIM ServiceProviderConfig endpoint: {bulk: {supported: true, maxOperations: N, maxPayloadSize: M}}
Known gotchas
bulkId references are only valid within a single BulkRequest; they cannot reference resources from a previous bulk request — treat cross-request bulkId references as invalid
failOnErrors: 0 means 'never stop on errors, process all operations'; it does NOT mean 'fail on the first error' — the semantics are the opposite of what the name suggests to many developers
The location in the BulkResponse for a POST operation is the newly created resource's URI; consumers use this to resolve bulkId references after the response — ensure the location is correct and absolute
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