Claim a Blinq step
Requires the paired Blinq server's credential in the Authorization bearer header; tenant and administrator credentials do not grant this authority. Generated from the production route registered in `internal/features/runners/inbound/http.go`. Long-polls for up to 20 seconds for one eligible queued step. Requires a live paired Blinq server credential; the service, secret and node are rechecked on every poll. The Blinq must be in both the node's fixed issued scope and its current hosting service, and this server must have announced the run's accepted version. Only active personally owned external hires with an unexpired run and a current active bound owner identity qualify. Identity cutoffs/bindings are checked against the original hire, so a later automatic admission cannot renew removed access. Ineligible-owner queued runs are canceled with audit and receive no claim. Credits and model budgets do not affect assignment. Assignment, generation increment and audit commit together; competing servers cannot receive the same step. Returns 204 when no eligible step is found. The response includes the shown-once per-claim execution_authority, bound to this server, organization, owner, hire and run; it must accompany the server credential on context/model/transition requests.
/v1/runner/blinqs/tasks/claimRequires the paired Blinq server's credential in the Authorization bearer header; tenant and administrator credentials do not grant this authority. Generated from the production route registered in internal/features/runners/inbound/http.go. Long-polls for up to 20 seconds for one eligible queued step. Requires a live paired Blinq server credential; the service, secret and node are rechecked on every poll. The Blinq must be in both the node's fixed issued scope and its current hosting service, and this server must have announced the run's accepted version. Only active personally owned external hires with an unexpired run and a current active bound owner identity qualify. Identity cutoffs/bindings are checked against the original hire, so a later automatic admission cannot renew removed access. Ineligible-owner queued runs are canceled with audit and receive no claim. Credits and model budgets do not affect assignment. Assignment, generation increment and audit commit together; competing servers cannot receive the same step. Returns 204 when no eligible step is found. The response includes the shown-once per-claim execution_authority, bound to this server, organization, owner, hire and run; it must accompany the server credential on context/model/transition requests.
Authorization
blinqServerCredential Credential issued to one paired Blinq server. Its prefix must match its stored node kind; its node, pairing secret and service must remain active. It conveys no tenant identity and stays inside the runner route fence. Neither a dlrt_ service secret nor an ordinary dlra_ runner credential substitutes for it.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Optional body: omit it, send an empty object or send null. At most 1 KiB; identity and selection fields, unknown fields and multiple JSON values are refused.
Optional body: omit it, send an empty object or send null. At most 1 KiB; identity and selection fields, unknown fields and multiple JSON values are refused.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/runner/blinqs/tasks/claim" \ -H "Content-Type: application/json" \ -d '{}'{ "execution_authority": "string", "task_id": "736fde4d-9029-4915-8189-01353d6982cb", "run_id": "dded282c-8ebd-44cf-8ba5-9a234973d1ec", "agent_id": "2b1e3b65-2c04-4fa2-a2d7-467901e98978", "blinq_id": "163ce100-8211-4522-93e1-e382b5984dbb", "version": 1, "manifest_digest": "string", "job_id": "string", "trigger_kind": "activation", "configuration": {}, "checkpoint": null, "checkpoint_revision": 0, "checkpoint_schema_version": 1, "state": null, "state_revision": 0, "occurrence": { "local_date": "2019-08-24", "due_at": "2019-08-24T14:15:22Z", "time_zone": "string" }, "claim_generation": 1, "lease_until": "2019-08-24T14:15:22Z", "deadline_at": "2019-08-24T14:15:22Z"}Commit progress under a live Blinq claim
undefined Generated from the production route registered in `internal/features/runners/inbound/http.go`. Requires assigned server bearer AND live X-Blinq-Claim-Authority. Generation and expected checkpoint revision fence one atomic checkpoint/receipt/audit commit under revocation/hire/run locks. Continue increments revision, retains claim/generation/lease and acknowledges identical receipt replay only while the claim is live. Different content for a recorded identity conflicts. Finish/fail terminate run/task and clear authority; terminal, expired, replaced and revoked workers are refused, including terminal retries. Fail stores workflow_failed on the run and its bounded category on the task. Current bound owner membership is rechecked under shared identity locks before hire/run locks. Removed owners get403 blinq_owner_inactive after their run/task cancellation and authority invalidation commit with audit. Credits and budgets are not checked, so free effects and previously paid saved text still deliver when credits run out. Typed notify and revision-checked set_state commit with the checkpoint and audit. Once-key receipts suppress duplicate delivery across runs and report already_delivered. Stale state rolls everything back. Expiry during a commit also rolls it back. Ask/approve remain unsupported. Response is not cacheable.
Announce a Blinq version
Requires the paired Blinq server's credential in the Authorization bearer header; tenant and administrator credentials do not grant this authority. Generated from the production route registered in `internal/features/runners/inbound/http.go`. Requires a live paired Blinq server. The Engine rechecks the service, secret and node under locks; the Blinq must be both in the node's fixed issued scope and currently approved for that hosting service. A new manifest within the approval is stored as accepted; one requesting more is stored as pending. A newly accepted version becomes current when its number is highest, unless an administrator has set a pin; arrival order never wins. Identical content for the same version returns the stored record and binds this server to it; different content conflicts. Stored versions, server bindings and any promotion commit with their audit record, and semantic refusals are audited. The digest freezes the description, not the deployed code. This operation does not change availability or enable catalog publication, hiring or execution.