Reference

You are in the deep end

Frozen request and response examples. They are not a live OpenAPI spec. The story is how it hangs together.

Stub headers: stub auth. Site layout: working on the docs.

Auth

File	What
stub auth	Channel `Bearer stub` + `X-Stub-Claims`; workload `Bearer fabric-internal` + `X-Workload`

POST /v1/intent/decide

File	What
decide-chat-request.json	Chat decide request
decide-chat-route.json	Chat decide `outcome=route` (`fee_explain`)
decide-chat-clarify.json	Chat decide `outcome=clarify`
decide-chat-abstain.json	Chat decide `outcome=abstain`
decide-jobs-route.json	Jobs decide (`ingress: "jobs"`, `route_id` set)

POST /v1/assistant/turns

File	What
assistant-turn-request.json	Chat turn body
assistant-turn-accepted.json	Chat turn accepted

POST /v1/jobs

File	What
jobs-start.json	Start `fee_explain`
jobs-start-claims-adjudicate.json	Start `claims_adjudicate`
jobs-accepted.json	`202 { "correlation_id" }`

POST /v1/runs

File	What
run-start.json	AR start after pin
run-status-completed.json	Run status `completed`

File	What
capability-account-fee-lookup.json	Domain capability `account_fee_lookup`
capability-ocr-extract.json	Domain capability `ocr_extract`
capability-extract-fields.json	Domain capability `extract_fields` (classify `output_schema`)
capability-start-contract-review.json	Agent-start capability `start_contract_review` → `contract_review`
capability-start-kyc-onboarding.json	Agent-start capability `start_kyc_onboarding` → `kyc_onboarding`
manifest-fee-explain.json	Manifest for `fee_explain`
manifest-fraud-investigate.json	Parent manifest `fraud_investigate` (Legal start)
manifest-ops-start-kyc.json	Parent manifest `ops_start_kyc` (KYC start)