intents_propose

POST

/intents/{intent_id}/proposal

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 template must exist and the intent must not yet have a proposal. Evidence will be extracted from the proposed solution, then validated against the template and intent. Upon success, a proof is generated.

Parameters

Path Parameters

intent_id

required

Unique identifier for an intent, assigned by the caller.

string format: uuid

Intent ID

Request Body ^required

Media type application/json

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 ZK proof generation to verify the proposal satisfies the intent’s template constraints.

object

metadata

required

Additional metadata shared with the evidence layer.

The content is agreed between the template provider and evidence layer.

solution

required

Identifier of the proposed solution.

Examples include a URL, a UCP product variant ID, or another identifier agreed between the template provider and evidence layer.

string

Example ^generated

{
  "metadata": "example",
  "solution": "example"
}

Responses

200

Proposal accepted, proving started

400

Bad request

Media type application/json

object

message

required

string

Example ^generated

{
  "message": "example"
}

409

Intent already has a proposal

Media type application/json

object

message

required

string

Example ^generated

{
  "message": "example"
}

500

Internal error

Media type application/json

object

message

required

string

Example ^generated

{
  "message": "example"
}