List proposals
Returns the organization's nightly role candidate proposals, optionally filtered by venture slug or decision status.
GET /v1/agent/proposals
| Address | https://api.hanzo.ai/v1/agent/proposals |
| Method | GET |
| Operation | get_agent_proposals |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the organization's nightly role candidate proposals, optionally filtered by venture slug or decision status.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
venture | query | string | — | Venture filters proposals to a single venture slug when non-empty. |
status | query | string | — | Status filters proposals by state (pending, approved, rejected) when non-empty. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | agent.proposalList | ok |
default | problem-details | refused |
200 body — 21 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
proposals | body | agent.RoleProposal[] | — | Proposals are the matching role candidate proposals, newest first. |
proposals[].agentId | body | string | — | AgentID is the created agent's handle (agent_...) once the proposal has been approved; empty when pending or rejected. |
proposals[].cap_micro_usd | body | integer (int64) | — | CapMicroUSD is the period budget cap in integer micro-USD that will be set on the created agent. |
proposals[].createdAt | body | integer (int64) | — | CreatedAt is when the proposal was generated, as Unix seconds. |
proposals[].decidedAt | body | integer (int64) | — | DecidedAt is when the proposal was approved or rejected, as Unix seconds. |
proposals[].decidedBy | body | string | — | DecidedBy records the subject who approved or rejected the proposal. |
proposals[].decisionReason | body | string | — | DecisionReason records the operator's note when approving or rejecting. |
proposals[].estimatedMicroUsd | body | integer (int64) | — | EstimatedMicroUSD is the estimated monthly spend for this role in integer micro-USD. |
proposals[].examples | body | string[] | — | Examples are the concrete failed runs, unsupported claims, or review bottlenecks backing the proposal. |
proposals[].function | body | string | — | Function is the studio function this role candidate belongs to. |
proposals[].id | body | string | — | ID is the stable proposal identifier (prop_...). |
proposals[].instructions | body | string | — | Instructions is the system prompt that will govern the proposed role. |
proposals[].max_task_micro_usd | body | integer (int64) | — | MaxTaskMicroUSD is the single-run budget ceiling in integer micro-USD that will be set on the created agent. |
proposals[].name | body | string | — | Name is the org-unique agent handle that will be created if the proposal is approved. |
proposals[].period | body | string | — | Period is the budget reset window: day, week, or month. |
proposals[].rationale | body | string | — | Rationale explains why the nightly review proposed this role candidate. |
proposals[].reportingLine | body | string | — | ReportingLine is the manager agent handle (parent) the proposed role reports to. |
proposals[].status | body | string | — | Status is the proposal's decision state: pending, approved, or rejected. |
proposals[].title | body | string | — | Title is the human-readable title of the proposed role. |
proposals[].tools | body | string[] | — | Tools are the MCP tool names the proposed role will be granted. |
proposals[].venture | body | string | — | Venture is the venture slug the role candidate is proposed for. |
Failure carries the platform error shape — see Errors.
Examples
hanzo agent proposals listimport { Configuration, AgentApi } from 'hanzoai';
const api = new AgentApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAgentProposals();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AgentApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AgentApi(client).get_agent_proposals()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.AgentAPI.GetAgentProposals(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, agent_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = agent_api::get_agent_proposals(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.AgentApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new AgentApi(client).getAgentProposals();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/agent/proposals \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches agent through the agent tool, which names its 51 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_agents"
}
}
}'