Files
zeekay 645325a641 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:53 -07:00

89 lines
2.8 KiB
C++

/**
* 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
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* EngineApi.h
*
*
*/
#ifndef HANZO_API_EngineApi_H_
#define HANZO_API_EngineApi_H_
#include "hanzo/ApiClient.h"
#include "hanzo/AnyType.h"
#include "hanzo/model/EngineStatus.h"
#include <cpprest/details/basic_types.h>
#include <boost/optional.hpp>
namespace hanzo {
namespace api {
using namespace hanzo::model;
class EngineApi
{
public:
explicit EngineApi( std::shared_ptr<const ApiClient> apiClient );
virtual ~EngineApi();
/// <summary>
/// Read one model&#39;s load state on the serving runtime
/// </summary>
/// <remarks>
/// Model reads one model&#39;s load state — loaded, unloading, or not_found, as the engine itself reports it.
/// </remarks>
/// <param name="model">Model is the model id to inspect, exactly as the model list reports it. (optional, default to utility::conversions::to_string_t(&quot;&quot;))</param>
pplx::task<std::shared_ptr<AnyType>> engineModel(
boost::optional<utility::string_t> model
) const;
/// <summary>
/// List the models the serving runtime holds, with each one&#39;s load state
/// </summary>
/// <remarks>
/// Models lists the models the engine serves, each with its load state — the server&#39;s own model table (its standard list envelope, load status included), relayed verbatim.
/// </remarks>
pplx::task<std::shared_ptr<AnyType>> engineModels(
) const;
/// <summary>
/// Whether the serving runtime is reachable, and which build it runs
/// </summary>
/// <remarks>
/// Status reports whether the engine deployment is reachable and which build revision it runs — an honest lens for \&quot;is the serving runtime up\&quot;, never a fabricated ok.
/// </remarks>
pplx::task<std::shared_ptr<EngineStatus>> engineStatus(
) const;
/// <summary>
/// The serving host&#39;s own inventory: devices, memory and build capabilities
/// </summary>
/// <remarks>
/// System reads the engine host&#39;s inventory: OS, CPU, memory, every accelerator device with its VRAM and compute capability, and the build&#39;s capabilities (CUDA/Metal/flash-attention) — the real hardware under the serving runtime, relayed verbatim.
/// </remarks>
pplx::task<std::shared_ptr<AnyType>> engineSystem(
) const;
protected:
std::shared_ptr<const ApiClient> m_ApiClient;
};
}
}
#endif /* HANZO_API_EngineApi_H_ */