List implementations

Returns the canonical implementation records with their citations.

GET /v1/patent/implementations

Addresshttps://api.hanzo.ai/v1/patent/implementations
MethodGET
Operationget_patent_implementations
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the canonical implementation records with their citations. ?idea= is the query the record exists to answer: which artifacts rest on this one conception entry.

Request

3 fields.

FieldInTypeRequiredDescription
idquerystring—ID reads one implementation.
ideaquerystring—Idea narrows to implementations citing one conception entry — which is how a correction finds every artifact built on the idea it invalidates.
projectquerystring—Project narrows to one project.

Response

StatusBodyMeaning
200patent.implsOutok
defaultproblem-detailsrefused

200 body — 22 fields.

FieldInTypeAlwaysDescription
databodypatent.PatentImplementation[]—Data are the canonical records, oldest append first.
data[].artifact_sha256bodystring—ArtifactSHA256 is the digest of the recorded artifact — a diff, a file, a build — when the caller has one and wants it addressed by content.
data[].authored_bybodystring—AuthoredBy is the validated principal who recorded this.
data[].canonicalbodyboolean—Canonical is DERIVED on read.
data[].content_hashbodystring—ContentHash is the server's digest of the recorded content.
data[].generatedbodyboolean—Generated says the recorded artifact was produced with a model's assistance rather than typed by hand.
data[].git_branchbodystring—GitBranch is the branch that commit was on.
data[].git_dirtybodyboolean—GitDirty says the working tree carried uncommitted changes when this was recorded.
data[].git_shabodystring—GitSHA is the commit.
data[].human_reviewbodystring—HumanReview is what a person did with the output: accepted, edited, rewritten, or none.
data[].idbodystring—ID is this implementation's stable id — usually the artifact or change it records, e.g. router-v2-generated.
data[].idea_idsbodystring[]—IdeaIDs names the conceptions this implements.
data[].modelbodystring—Model names the system that produced the code, as it was addressed.
data[].notesbodystring—Notes is anything a later reader needs.
data[].projectbodystring—Project is the SERVER's scope value.
data[].prompt_sha256bodystring—PromptSHA256 is the digest of the prompt, not the prompt.
data[].recorded_atbodystring—RecordedAt is the server's clock.
data[].repobodystring—Repo is the repository the work landed in.
data[].revisionbodystring—Revision is original, corrected or retracted.
data[].seqbodyinteger (int64)—Seq is the append order, which is what GET /v1/patent/proof compares against the cited ideas.
data[].visibilitybodystring—Visibility is private, org or public; forced private on a write.
totalbodyinteger (int64)—Total is len(data).

Failure carries the platform error shape — see Errors.

Examples

hanzo patent implementations get
import { Configuration, PatentApi } from 'hanzoai';

const api = new PatentApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPatentImplementations();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PatentApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PatentApi(client).get_patent_implementations()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.PatentAPI.GetPatentImplementations(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, patent_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = patent_api::get_patent_implementations(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PatentApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new PatentApi(client).getPatentImplementations();

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 https://api.hanzo.ai/v1/patent/implementations \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches patent through the patent tool, which names its 12 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_patent_approvals"
         }
       }
     }'

Patent API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.