Hanzo
OpenapiGraph

The relations in use, and the rule that resolves a conflict

The relations in use, and the rule that resolves a conflict

GET /v1/graph/vocabulary

Addresshttps://api.hanzo.ai/v1/graph/vocabulary
MethodGET
OperationgraphVocabulary
AuthAuthorization: Bearer $HANZO_API_KEY

The relations in use, and the rule that resolves a conflict

Request

GET /v1/graph/vocabulary takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200graphVocabularyOutok

200 body — 3 fields.

FieldInTypeAlwaysDescription
boundbodyintegerBound is the ceiling on one walk.
relationsbodystring[]Relations is what this organization has actually asserted, which is the only vocabulary there is: this plane declares none of its own.
rulebodystring[]Rule names the terms of the precedence order, in the order they apply.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Graph API · All Hanzo APIs · Interactive reference

How is this guide?

On this page