§ 02 · Deployment APIRead rows, create intent
The product contract is ready for operators. The endpoint must still prove itself.عقد المنتج جاهز للمشغلين. لكن على النقطة إثبات نفسها.
The deployed endpoint becomes real only when the backend receives matching load proof from the serving layer for the deployment id, adapter id, base model, mode, endpoint id, and checksum. Endpoint smoke then has to prove a funded deterministic request, response hash, latency, token totals, and adapter trace. The POST route is live only as a disabled validation contract that returns 409 and records nothing. Until then, deployment rows are planning and audit records, not public route promises.
curl -s "https://api.dcp.sa/api/adapters/deployments?limit=25" \
-H "Authorization: Bearer $DCP_RENTER_KEY"
curl -s https://api.dcp.sa/api/adapters/adpt_support_arabic/deployments \
-H "Authorization: Bearer $DCP_RENTER_KEY" \
-H "Content-Type: application/json" \
-d '{
"deployment_id": "adpl_support_arabic_001",
"mode": "single_adapter_live_merge",
"endpoint_id": "endpoint_qwen_arabic_01",
"route_traffic": false
}'
curl -s https://api.dcp.sa/api/adapters/endpoints/smoke/readiness
curl -s https://api.dcp.sa/api/adapters/$ADAPTER_ID/deployments/$DEPLOYMENT_ID/endpoint-smoke \
-H "Authorization: Bearer $DCP_RENTER_KEY"
curl -s https://api.dcp.sa/api/adapters/$ADAPTER_ID/deployments/$DEPLOYMENT_ID/endpoint-smoke \
-X POST \
-H "Authorization: Bearer $DCP_RENTER_KEY" \
-H "Content-Type: application/json" \
-d '{"funded_smoke_principal":true,"smoke_result":{"request_id":"req_smoke_001"}}'
curl -s https://api.dcp.sa/api/adapters/usage/attribution/readiness
curl -s https://api.dcp.sa/api/adapters/settlement/readiness
curl -s https://api.dcp.sa/api/adapters/billing/approval/readiness
curl -s https://api.dcp.sa/api/adapters/billing/readiness- Single-adapter live merge is first; multi-LoRA waits for controlled vLLM smoke.
- Route traffic remains false until deployment, adapter, base model, mode, endpoint, and checksum proof match.
- Usage writes and billed inference start only after endpoint smoke proves response hash, latency, token totals, adapter trace, funded principal, usage attribution, and settlement policy.
