Authenticate to Guidewire Cloud using OAuth 2.0 client credentials; obtain an access token scoped to the ClaimCenter resource server for your tenant
Look up the policy by policy number using the PolicyCenter data API or the ClaimCenter policy search endpoint; validate that the loss date falls within the policy effective period and that the reported loss type is covered under the policy
Submit the FNOL (First Notice of Loss) via the ClaimCenter claims POST endpoint with the required fields: policy reference, loss date, loss cause, loss location, claimant information, and a contact for the insured
After the claim is created, retrieve the claim number and the auto-assigned adjuster from the response; create an initial reserve using the coverage-specific reserve endpoint with the coverage reference, reserve line type, and initial reserve amount
Consume the ClaimCenter webhooks for claim status changes; when the claim moves from OPEN to COVERAGE_UNDER_REVIEW, trigger an internal workflow to gather additional documentation from the insured
Poll the claim activities endpoint to surface any adjuster-created tasks that require external data input (e.g., a request for a repair estimate) and route them to the appropriate internal team via your task management system
Known gotchas
Guidewire Cloud API tenant endpoints are environment-specific (dev, test, production) and use separate OAuth client credentials per environment; using production credentials against a test environment or vice versa will fail authentication silently if the endpoints share a domain pattern
Reserve entries in ClaimCenter must reference a valid coverage segment on the claim; if the coverage mapping from your FNOL data to ClaimCenter's coverage hierarchy is incorrect, the reserve POST will return a 422 with a validation error rather than creating a reserve on the wrong coverage
ClaimCenter's FNOL endpoint may trigger downstream workflows (assignment rules, reserve thresholds, regulatory reporting) synchronously on submission; a slow or failed downstream step can cause the FNOL POST to time out at the API layer — implement retry with idempotency on FNOL submission
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