Beta · unsigned

Which AI tool can actually run your workload?

Discover the parts, inspect their evidence, then resolve a pinned recipe—or get a refusal that names exactly what is missing.

Public accessread only
curl -s "https://resolve.hiqs.ai/api/public/registry?action=list"
Catalog
Five distinct kinds
Recipes
Pinned + evidence-dated
Decision
One route or refusal

Local runtimes document on-device execution. A recipe may pin a gateway for a hosted route or a runtime for a local route when compatible evidence exists.

Live catalog ledger

Just added

View all

Evidence ledger

From catalog record to verifiable recipe

Open Workbench

Recipe system

Pin what must work together

Preview
01

Harness + model

Record exact identities and revisions.

02

Gateway or runtime

Choose a hosted or local execution path.

03

Dated evidence

Attach outcomes, scope, and expiry.

04

Replayable decision

Lock the policy and resulting route.

No approved recipe gallery is shown yet. Recipe records will appear only after their evidence and review path are live.

Resolver contract

A useful no is still an answer

The resolver does not silently substitute, guess, or hide missing evidence.

NO_SERVING_BINDING

The model is known, but no eligible serving route is recorded.

UNVERIFIED_CLAIM

The route depends on evidence below the policy threshold.

INSUFFICIENT_PIN

The identity is too loose for the requested reproducibility.

Keep identities precise

Five kinds. No category collapse.

A model is not its gateway. A harness is not a service. A runtime makes local execution inspectable without pretending it is a hosted route.

Trust model

Evidence before execution.

Discover

Find published records by kind without flattening their identities.

Inspect

Read sources, revisions, claims, pins, and explicit unknowns.

Resolve

Apply a written policy to a pinned route or local recipe.

Refuse

Receive a stable reason code when evidence cannot support a route.