API referenceEndpoints

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.

POST/v1/runner/blinqs/versions

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.

Authorization

blinqServerCredential
AuthorizationBearer <token>

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.

One JSON manifest, with a 64 KiB request-body and canonical-manifest limit. Unknown manifest, permission and limit fields are refused. Omitted permissions and limits grant nothing; the manifest requests authority and cannot grant it.

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/versions" \  -H "Content-Type: application/json" \  -d '{    "blinq_id": "163ce100-8211-4522-93e1-e382b5984dbb",    "version": 1,    "jobs": [      "string"    ],    "configuration_schema": {},    "checkpoint_schema_version": 1  }'
{  "blinq_id": "163ce100-8211-4522-93e1-e382b5984dbb",  "version": 1,  "status": "accepted",  "digest": "string",  "manifest": {    "blinq_id": "163ce100-8211-4522-93e1-e382b5984dbb",    "version": 1,    "jobs": [      "string"    ],    "latest_only_jobs": [      "string"    ],    "permissions": {      "inbox_actions": [        "string"      ],      "models": [        "string"      ],      "tools": [        "string"      ],      "context": [        "string"      ]    },    "limits": {      "max_model_calls": 0,      "max_input_tokens": 0,      "max_output_tokens": 0,      "max_cost_micros": 0    },    "configuration_schema": {},    "checkpoint_schema_version": 1,    "presentation": {      "name": "string",      "description": "string",      "color": "string",      "avatar": "string",      "details": "string"    },    "activation_job": "string",    "managed_schedule": {      "job_id": "string",      "cron": "string"    }  },  "created_at": "2019-08-24T14:15:22Z"}