What is in force about an entity as of an instant, and what disagreed
What is in force about an entity as of an instant, and what disagreed
POST /v1/graph/resolve
| Address | https://api.hanzo.ai/v1/graph/resolve |
| Method | POST |
| Operation | graphResolve |
| Auth | Authorization: Bearer $HANZO_API_KEY |
What is in force about an entity as of an instant, and what disagreed
Request
3 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
as_of | body | string | — | AsOf is the instant to answer at, RFC 3339. |
entity | body | string | — | Entity is the thing to answer about. |
relation | body | string | — | Relation is the one relation to settle. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | graphResolveOut | ok |
200 body — 32 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
as_of | body | string | — | AsOf is the instant this answer was taken at, RFC 3339: the one asked for, or the server's clock when none was. |
conflicts | body | wireFact[] | — | Conflicts is every OTHER assertion knowable at AsOf, strongest first. |
conflicts[].at | body | string | — | At is when the thing was so, RFC 3339, as the asserter gave it. |
conflicts[].by | body | string | — | By is the identity that filed it — owner or owner/user — stamped from the validated principal at the write, never from the body. |
conflicts[].confidence | body | number | — | Confidence in [0,1] as the asserter gave it; absent is 0. |
conflicts[].entity | body | string | — | Entity is the thing described, in the organization's own namespace. |
conflicts[].evidence | body | string | — | Evidence points at the record the claim came from. |
conflicts[].id | body | string | — | ID is the assertion's content address, minted by the server from what was asserted. |
conflicts[].knowable | body | string | — | Knowable is the first instant this plane could have answered with the assertion, RFC 3339: the later of Seen and the server's clock at the write. |
conflicts[].names | body | boolean | — | Names true means the assertion is an edge and Value is an entity. |
conflicts[].relation | body | string | — | Relation is what was asserted of it. |
conflicts[].seen | body | string | — | Seen is when the asserter says it became knowable, RFC 3339. |
conflicts[].source | body | string | — | Source names who asserted, as the caller gave it. |
conflicts[].value | body | string | — | Value is what the relation points at: another entity's key when Names is true, otherwise a scalar. |
contested | body | boolean | — | Contested is true when at least one conflict claims a value different from the winner's. |
entity | body | string | — | Entity is the entity the question named, echoed so a stored answer still says what it is about. |
known | body | boolean | — | Known is false when this plane held nothing knowable at AsOf. |
relation | body | string | — | Relation is the relation the question named, echoed for the same reason. |
truncated | body | boolean | — | Truncated says this pair holds more assertions than one read returns, so the winner was decided from the most recent ceiling-full of them. |
winner | body | wireFact | — | |
winner.at | body | string | — | At is when the thing was so, RFC 3339, as the asserter gave it. |
winner.by | body | string | — | By is the identity that filed it — owner or owner/user — stamped from the validated principal at the write, never from the body. |
winner.confidence | body | number | — | Confidence in [0,1] as the asserter gave it; absent is 0. |
winner.entity | body | string | — | Entity is the thing described, in the organization's own namespace. |
winner.evidence | body | string | — | Evidence points at the record the claim came from. |
winner.id | body | string | — | ID is the assertion's content address, minted by the server from what was asserted. |
winner.knowable | body | string | — | Knowable is the first instant this plane could have answered with the assertion, RFC 3339: the later of Seen and the server's clock at the write. |
winner.names | body | boolean | — | Names true means the assertion is an edge and Value is an entity. |
winner.relation | body | string | — | Relation is what was asserted of it. |
winner.seen | body | string | — | Seen is when the asserter says it became knowable, RFC 3339. |
winner.source | body | string | — | Source names who asserted, as the caller gave it. |
winner.value | body | string | — | Value is what the relation points at: another entity's key when Names is true, otherwise a scalar. |
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.
import { Configuration, GraphApi } from 'hanzoai';
const api = new GraphApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.graphResolve({ as_of: "<as_of>", entity: "<entity>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import GraphApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = GraphApi(client).graph_resolve(as_of="<as_of>", entity="<entity>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GraphAPI.GraphResolve(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, graph_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = graph_api::graph_resolve(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.GraphApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new GraphApi(client).graphResolve();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 -X POST https://api.hanzo.ai/v1/graph/resolve \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"as_of": "<as_of>",
"entity": "<entity>"
}'The door declares no tool for graph — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?