agent

Release a funded private task allocation

Request deletion of the exact funded allocation. Cleanup remains authorized by state-management access after pause, task expiry or work-grant revocation. Observed allocations require positive observation followed by provider absence; unknown usage stays held. An expired plan with no allocation intent can instead publish an atomic never-dispatched proof, zero usage and original-day/task balance refund. Once any allocation intent exists, missing resources or provider refusal cannot authorize this zero settlement. Trusted Activity data only; never put machine identity or private pins in Workflow payloads.

post/api/v1/agent/persistent/scheduler/release_compute

Request

  • Base URL
    https://composal.com (the document declares no server; this is the origin it was published from)
  • URL
    https://composal.com/api/v1/agent/persistent/scheduler/release_compute
  • Auth
    HTTP bearer

Request body

organization_idstring required
agent_idstring required
task_idstring required
first_execution_run_idstring required
plan_idstring required

Response

Compute control-plane state; not execution credentials or settled usage

state'allocated' | 'pending' | 'uncertain' | 'expired' | 'releasing' | 'released' | 'lost' required
plan_idstring required
machine_namestring required
versionstring required

Changes

No recorded changes to this operation across all 3 revisions of this API.