# POST /v1/decisions/{token} — Submit Decision on Estimate or Change Order

> POST /v1/decisions/{token} — Submit Decision on Estimate or Change Order is a paid API for AI agents from zero-plan-cost.zack-2ab.workers.dev, paid per call via MPP, price unknown, status unknown (last checked 2026-10-20).

Submits a client decision (approval or rejection) for a project estimate or change order identified by a token

## Facts

- Endpoint: POST https://zero-plan-cost.zack-2ab.workers.dev/v1/decisions/{token}?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Provider: zero-plan-cost.zack-2ab.workers.dev
- Website: https://zero-plan-cost.zack-2ab.workers.dev
- Canonical page: https://www.zero.xyz/c/zero-plan-cost-zack-2ab-workers-dev-post-v1-decisions-token-submit-4d9c050e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pAMsKvCN9_1ZDagKQSfra

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability zero-plan-cost-zack-2ab-workers-dev-post-v1-decisions-token-submit-4d9c050e -d '<json body>'
```

Example prompt: My client just approved the estimate — can you record their approval decision using token abc123xyz so the project can move forward?

## When to prefer this

Use this endpoint when a client has reviewed a project estimate or change order (typically received as a PDF via email) and needs to formally record their approval or rejection. This is the write/submission counterpart to GET /v1/decisions/{token} which retrieves the decision form or status.

## Known failure modes

- Invalid or expired token returns 404 or 400 error
- Missing required decision payload returns 422 validation error
- Token already used or decision already recorded returns 409 conflict
- Malformed request body returns 400 bad request
- Network or worker timeout returns 500 or 503

## Output

Returns a confirmation that the client's decision (approval or rejection) has been recorded against the estimate or change order associated with the provided token, likely including updated status of the estimate or project.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zero-plan-cost-zack-2ab-workers-dev-post-v1-decisions-token-submit-4d9c050e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from zero-plan-cost.zack-2ab.workers.dev](https://www.zero.xyz/host/zero-plan-cost.zack-2ab.workers.dev/llms.txt)