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

70 lines
2.2 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.
*/
/*
* ExplorerApi.h
*
*
*/
#ifndef HANZO_API_ExplorerApi_H_
#define HANZO_API_ExplorerApi_H_
#include "hanzo/ApiClient.h"
#include "hanzo/model/IndexersOut.h"
#include "hanzo/model/OraclesOut.h"
#include <boost/optional.hpp>
namespace hanzo {
namespace api {
using namespace hanzo::model;
class ExplorerApi
{
public:
explicit ExplorerApi( std::shared_ptr<const ApiClient> apiClient );
virtual ~ExplorerApi();
/// <summary>
/// Reports the deployment&#39;s chain indexer(s) and how far each has indexed.
/// </summary>
/// <remarks>
/// Reports the deployment&#39;s chain indexer(s) and how far each has indexed. Identity and health come from the indexer&#39;s /health; the latest indexed block (height + time) from its /v1/explorer/blocks. The row EXISTS if EITHER call reaches the indexer; when the indexer is entirely unreachable the answer degrades to an honest-EMPTY list at 200, not a 502. No chain HEAD is exposed by the indexer REST, so &#x60;lag&#x60; is honestly omitted rather than fabricated.
/// </remarks>
pplx::task<std::shared_ptr<IndexersOut>> getExplorerIndexers(
) const;
/// <summary>
/// Reports the on-chain price/data oracles from the graph&#39;s O-Chain PriceFeed registry.
/// </summary>
/// <remarks>
/// Reports the on-chain price/data oracles from the graph&#39;s O-Chain PriceFeed registry. A reachable graph with no feeds answers an honest empty list; an unreachable or erroring graph likewise degrades to an empty list at 200 rather than a 502, so the console never error-toasts. No feed is ever fabricated.
/// </remarks>
pplx::task<std::shared_ptr<OraclesOut>> getExplorerOracles(
) const;
protected:
std::shared_ptr<const ApiClient> m_ApiClient;
};
}
}
#endif /* HANZO_API_ExplorerApi_H_ */