hanzo-client 8.5.156

Generated client for the Hanzo API — every service, one crate.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

/*
 * Hanzo Cloud API
 *
 * The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
 *
 * The version of the OpenAPI document: v1
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct AiMcpSurface {
    /// Apps is one row per subsystem this deployment composes, in manifest order.
    #[serde(rename = "apps", skip_serializing_if = "Option::is_none")]
    pub apps: Option<Vec<models::AiMcpApp>>,
    /// Names are this process's own tool names, present only when the query asked for them.
    #[serde(rename = "names", skip_serializing_if = "Option::is_none")]
    pub names: Option<Vec<String>>,
    /// Tools is how many tools THIS PROCESS's MCP server carries: its own typed-op registry, projected. It is the only number a subsystem can state honestly — what the FLEET's server carries is a question only the host can ask, and it asks it by asking every subsystem (POST /v1/mcp, tools/list).
    #[serde(rename = "tools", skip_serializing_if = "Option::is_none")]
    pub tools: Option<i32>,
}

impl AiMcpSurface {
    pub fn new() -> AiMcpSurface {
        AiMcpSurface {
            apps: None,
            names: None,
            tools: None,
        }
    }
}