intents_propose
const url = 'https://example.com/intents/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/proposal';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"metadata":"example","solution":"example"}'};
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://example.com/intents/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/proposal \ --header 'Content-Type: application/json' \ --data '{ "metadata": "example", "solution": "example" }'Submit a proposal for a pending intent, triggering the delta mandate pipeline.
The intent and its policy must exist and the intent must not yet have a proposal. Evidence will be extracted from the proposed solution, then validated against the policy and intent. Upon success, a proof is generated.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Unique identifier for an intent, assigned by the caller.
Intent ID
Request Body required
Section titled “Request Body required ”An agent’s proposed solution for a specific intent.
Once submitted, the Orchestrator sends the solution to the evidence layer to extract evidence, then runs proof generation to verify the proposal satisfies the intent’s policy constraints.
object
Additional metadata shared with the evidence layer.
The content is agreed between the policy provider and evidence layer.
Identifier of the proposed solution.
Examples include a URL, a UCP product variant ID, or another identifier agreed between the policy provider and evidence layer.
Example generated
{ "metadata": "example", "solution": "example"}Responses
Section titled “ Responses ”Proposal accepted, proving started
Bad request
object
Example generated
{ "message": "example"}Intent already has a proposal
object
Example generated
{ "message": "example"}Internal error
object
Example generated
{ "message": "example"}