# Kiln Stash - Finalize Object

> Kiln Stash - Finalize Object is a paid API for AI agents from stash.fluidrack.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Finalizes a previously reserved TTL object slot in S3-compatible storage by confirming its SHA-256 hash, committing the artifact for agent retrieval.

## Facts

- Endpoint: POST https://stash.fluidrack.com/v1/objects/%7Bid%7D/finalize
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kiln-stash-finalize-object-82c6b6f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2-Ju3XL28zXzegtR_jSTZ

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 kiln-stash-finalize-object-82c6b6f9 -d '<json body>'
```

Example prompt: I just uploaded the artifact to the reserved slot — go ahead and finalize object ID 'a1b2c3d4' with SHA-256 hash 'e3b0c44298fc1c149afb4c8996fb92427ae41e4649b934ca495991b7852b855' to commit it to Kiln Stash.

## When to prefer this

Use this endpoint as the second step of a two-phase upload workflow after reserving a TTL object slot via the companion reserve endpoint. It is the correct choice when you need to commit an uploaded artifact with integrity verification via SHA-256 before making it available for agent retrieval. Prefer this over single-step storage APIs when your workflow requires a reserve-then-finalize pattern, especially in multi-agent pipelines where upload confirmation and integrity checking are critical.

## Known failure modes

- SHA-256 mismatch — provided hash does not match the uploaded content, causing rejection
- Invalid or expired object ID — the reservation slot has expired or does not exist
- Object already finalized — attempting to finalize an already-committed object
- Storage backend error — S3-compatible backend unavailable or write failure
- Missing required fields — either id or sha256 not provided in the request body

## How this service works

TTL artifact storage for AI agents backed by S3-compatible object storage.

## Output

A confirmation response indicating the object has been successfully finalized and committed to TTL storage, including the object ID and its verified status. The artifact is now available for retrieval by agents until its TTL expires.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string"
  },
  "sha256": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kiln-stash-finalize-object-82c6b6f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stash.fluidrack.com](https://www.zero.xyz/host/stash.fluidrack.com/llms.txt)