---
title: "Trigger Compute"
method: POST
path: "/aurd-apportionment/{claim_id}/compute"
tags: ["au-rd-apportionment"]
---

# Trigger Compute

`POST /aurd-apportionment/{claim_id}/compute`

## Request

- Base URL: `https://api.claimkit.co` (the document declares no server; this is the origin it was published from)
- URL: `https://api.claimkit.co/aurd-apportionment/{claim_id}/compute`
- Auth: none declared

Kick off an async compute run for the claim.

Admin-only. The compute itself is non-destructive (writes only to the
shadow `proposed_rd_percentage` column), but it consumes a background
execution slot, replaces per-activity apportionment splits, and
mutates the methodology_version annotation — so we gate it to admins
to mirror the activate / deactivate toggle. Returns 202 with the
AgentExecution id; clients poll the GET endpoint for completion.

## Path parameters

- `claim_id` integer, required

## Response `202`

Successful Response

- ApportionmentRunStatus: Status payload returned by both the POST (immediately) and the GET (when polling for completion).
  - `status` string, required
  - `job_id` string, nullable
  - `methodology_version` string, required
  - `error` string, nullable
  - `started_at` string, nullable
  - `completed_at` string, nullable
  - `in_scope_count` integer, nullable
  - `out_of_scope_count` integer, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/claimkit/apis/claimkit-api.md) - [All operations](https://skmtc.dev/claimkit/apis/claimkit-api/llms.txt) - [OpenAPI document](https://skmtc.dev/claimkit/apis/claimkit-api/revisions/94dc85ba5326?raw)