Pull Agent Config
const url = 'https://aura-api-eu.strangeworks.com/api/v1/projects/example/agent-config/pull';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"from_deployment":"example","instructions":true,"skills":true}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://aura-api-eu.strangeworks.com/api/v1/projects/example/agent-config/pull \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "from_deployment": "example", "instructions": true, "skills": true }'Pull a deployment’s instructions and/or skills into this project’s deployment scope.
Config is separate from the workspace, so this is how a project takes the
operator’s current rules without workspace/checkout overwriting work in
flight. Replaces the deployment scope rather than merging into it, so a rule
the deployment retired stops applying here too. The project’s own scope is
untouched.
Under agent-config/ rather than beside the skills collection, where the verb
would collide with /skills/{skill} and reserve its name as an unusable skill.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”Which agent config to pull from a deployment into a project’s deployment scope.
Both default on, so the common “give me the operator’s current rules” needs no flags; either can be turned off to pull one kind without the other.
object
Responses
Section titled “Responses”Successful Response
object
Examplegenerated
{ "from_deployment": "example", "objects": 1}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}