Source statements, supported attribution and analytical conclusions have different meanings. A report keeps those distinctions visible. High, Medium or Low is shown only when its named evidence policy is satisfied; otherwise the result is Not assessed.
The /v1 fields below are a compatibility reference. A legacy score or interval is not a calibrated probability or the new report policy.
Private access, bounded execution
Approved existing tenant keys must be explicitly allowed into the pilot. Preview validates the values you enter and performs no research. Live requests need a separate server switch, an authorized purpose and positive configured per-key/day and aggregate spending limits. Browser controls cannot enable paid calls.
The playground keeps your key only in page memory. It never puts provider credentials in the browser or puts your key in a URL.
Choose the right product
Discover offers the full Individual report flow. Company quick checks are gated; deeper due diligence is on request. Trace is Coming soon.
Authentication
A bearer token on every request. Once you have an account, you mint and revoke
your own keys through the control plane. Each is shown once and stored only as a salted hash: we
cannot recover a key for you, and neither can anyone who reaches our database.
Scopes are separate on purpose. A key that opens inquiries cannot mint another key,
publish a policy or read the audit trail. Those need an admin key, which should
not be the one deployed to your application servers.
Test keys carry the gx_test_ prefix and reach the same surface against
non-production data.
Your first call
This is the whole integration for most teams. One request, one response, and the
two fields that matter are the score and the interval around it.
Read the interval, not just the score. 62 with an interval of 51–73 is a usable
answer. 62 with an interval of 15–85 is the system telling you it does not know, and
treating the two the same way is the most expensive mistake an integration can make. The width
is a function of how much evidence answered, and the response tells you that too.
Core concepts
Five things you declare or receive. Getting these right is most of a good
integration.
Concept
What it is
Why it exists
intent
What you are about to do: onboard, underwrite, authorise, expand a case.
Sets how hard the engine works and when it is allowed to stop.
purpose
The lawful basis for asking. Mandatory on every call, without exception.
It is written into the audit trail. When a regulator asks why you held this data,
the answer is a record rather than a recollection.
stake
What is at risk, how much, whether it is reversible, and how long you can wait.
Fixes how narrow the interval has to be before an answer is worth acting on. A
reversible listing tolerates doubt a wire transfer does not.
assessment
Score, interval, methodology version, as-of, and an evidence summary.
What the evidence supports. Never a decision, never a recommendation.
label
Your own band applied to that score, under a policy version you published.
Your risk appetite is not ours to guess. Changing a label changes an outcome;
changing a score would change history.
By domain
Seven industries, one surface. Each section below is the same API called with a
different declaration, which is the whole design: what differs between a lender and an
investigator is the question being asked, not the evidence or the endpoint.
Why there is no /v1/banking. A vertical endpoint would mean a vertical
model, and a vertical model cannot see the pattern that crosses them. The device applying for
credit this morning listed on a marketplace last week; the wallet receiving funds tonight was
named in a dating scam in March. One surface over one graph is what makes those the same
question.
Banking and lending
Whether to open an account or extend credit to somebody whose file is thin.
What gets missed today
A bureau tells you about a person's borrowing. It cannot tell you that the email address on the application is three weeks old, that the device has applied under four other names this month, or that the phone number was issued after the employment history it claims to support. None of that is on a credit file, and all of it is knowable before you decide.
What we add
Correlation across identifiers the applicant supplied separately. A clean record on each one and a damning pattern between them is the case this exists for.
Send outcomes. Repaid, defaulted, reversed: it is the only way an assessment learns your book rather than the average book.
Payments and fintech
Whether to authorise a transfer to a payee seen for the first time, inside the authorisation window.
What gets missed today
Rules catch what they were written for. A first-time payee at an unusual hour is either a fraud or a Tuesday, and the difference is not in the transaction. It is in what the payee's identifiers have been doing elsewhere.
What we add
A preliminary answer inside your deadline, refined afterwards rather than withheld. You get something usable in the window and something better after it.
Built for India first. UPI identifiers and DLT-registered SMS headers are first-class artifact types, not a generic string field with a note attached.
Crypto and digital assets
Whether to accept a deposit from, or release funds to, a wallet address.
What gets missed today
An address is either sanctioned or it is not, and every exchange checks that. The interesting question comes before it: has this address, or the cluster around it, been named in scam reporting, drained a contract, or appeared beside identifiers you have already refused.
What we add
Sanctions screening and community scam reporting on the same call, with the address treated as an artifact that can correlate to an email, a handle or a device rather than as a string in isolation.
Ten tools on wallet addresses, four of them at no cost, including sanctions lists and scam-address reporting.
Dating and social platforms
Whether a new profile is a person, and whether it is the person it says.
What gets missed today
Romance fraud does not fail a document check, because the documents are real and belong to somebody. What gives it away is the shape of the account: a handle claimed across nine platforms in a week, photographs that predate the profile, a phone number in one country and a device in another.
What we add
The broadest coverage we have. Eighteen tools on social handles, because this is where identity is thinnest and the correlation between an account, its age and its other appearances does the most work.
The assessment is about the account, not the human being behind it. We report what public evidence supports, and we do not infer protected characteristics.
Marketplaces and platforms
Whether to let a seller list, a driver drive, or a host host.
What gets missed today
Everything on the application is true. The seller is real, the address exists, the documents check out. What you cannot see is that the identifiers reuse a network already behind three suspended accounts, because that is a fact about your own platform's history joined to public evidence.
What we add
Your suspensions are testimony. Send them as observations and they weigh on future assessments, which no external vendor can do for you, because they do not have them.
Monitors matter here. An account that was fine at onboarding and is not fine now is the common case, and asking again on a schedule is the expensive way to find out.
Investigations
What happened, who was involved, and what you can put in front of a regulator or a court.
What gets missed today
The subject is a network, not a person. Several analysts touch it, the scope grows as it goes, and at the end somebody has to show their working to somebody who was not there.
What we add
Cases carry an authorisation record, a budget, a legal hold and an append-only event log. Every expansion is one deliberate, costed hop rather than an open-ended crawl, and the export is an evidentiary bundle rather than a screenshot.
Requires an investigative tenant. Every case needs an authorisation on the record before it opens, which is a constraint we are not willing to make optional.
Compliance and AML
Whether you can show, later, that you looked and what you found.
What gets missed today
Screening tools answer the question you asked on the day you asked it. What they rarely produce is the thing an examiner actually wants: which rule ran, on which version, against which evidence, and why the answer was what it was at that moment rather than today.
What we add
Every call writes one audit row carrying the purpose you declared, and every assessment names the methodology version that produced it. Your risk bands are a policy you publish and version here, so a label from March can be reconstructed in October without anybody relying on memory.
Scores never change retroactively. A published assessment is a fact about what the evidence supported at a moment; when your appetite changes you publish a new policy and the label changes, which is a different thing and is recorded as one.
Reference
Generated from the named source contract. This reference does not certify what is deployed.
Endpoints marked contract have a
reference shapes; availability depends on the deployed build and tenant. They are documented because integrating
against a shape that will not change is worth more than a surprise later.
Consent records
Authorized access to the gateway's consent record.
1 endpoint ·
/v1/consent
GET/v1/consent/{record_id}reference
Get Consent
One consent/retention record: what was retained, under which purpose, for how long.
Scoped to the calling tenant. A record that exists but belongs to
another tenant answers exactly like one that does not exist, so this
can never be used to learn whether a given id belongs to somebody
else's inquiry.
200ConsentRecordOut
Parameters
record_id
path
required
Trust private pilot
Release-candidate request/response playground. Approved tenant keys and server switches are required; paid execution is disabled by default.
2 endpoints ·
/v2/trust
POST/v2/trust/checksrelease candidate · gated
Trust Check
Validate, reserve and run one canonical check; live mode is separately disabled.
200TrustResponse
GET/v2/trust/schemarelease candidate · gated
Trust Schema
Describe the actual implemented pilot request body after authorization.
200no body
Report core
Authenticated report projection for a completed inquiry. Legacy evidence does not inherit canonical attribution or source-lineage guarantees.
Expose report-owned meaning for an already completed authorized inquiry.
200no body
Parameters
inquiry_id
path
required
profile
query
required
format
query
optional
Inquiries
Ask about a subject and get an assessment. This is the endpoint most integrations use and, for many, the only one they ever need.
3 endpoints ·
/v1/inquiries
POST/v1/inquirieslive
Open Inquiry
Open an inquiry (command OpenInquiry).
mode=sync waits for the answer within stake.deadline_ms. mode=async returns 202 the moment
the inquiry is admitted and runs it in the background, for a check too deep to hold a connection for
(S52): poll GET /v1/inquiries/{id} for reasoning, then the answer, which is kept a day. Every
refusal (a purpose, a limit, an unreadable material) still comes back at once, exactly as it does for
sync. stream is not served and is refused here rather than silently treated as sync.
Rejected with I13 when purpose is missing or not allowed by policy.
Every outcome, including a refusal, writes one audit row; its id comes
back on the X-Griffynx-Audit-Id header so a caller can cite the call
they made.
bodyInquiryRequest200InquiryResponse
GET/v1/inquiries/{inquiry_id}reference
Get Inquiry
The inquiry as it stands: reasoning while it runs, then its answer, kept a day (S52).
An inquiry that is not yours, does not exist or is more than a day old is not found, the same answer for
all three so this cannot be used to learn whether somebody else's exists (I19).
200InquiryResponse
Parameters
inquiry_id
path
required
GET/v1/inquiries/{inquiry_id}/eventsreference
Inquiry Events
SSE: AssessmentIssued, AssessmentRevised, InquiryConcluded. Replayable with after.
200no body
Parameters
inquiry_id
path
required
after
query
optional
Observations
Your own testimony about a subject. What you know that nobody else does enters here, carrying its provenance, and is weighed accordingly.
2 endpoints ·
/v1/observations
POST/v1/observationsreference
Submit Observation
Submit testimony (command SubmitObservation). Enters with its provenance class; never sets a score.
bodyObservationIn201ObservationOut
POST/v1/observations/batchreference
Submit Observations
Submit many observations at once.
bodyObservationIn[]201ObservationOut[]
Outcomes
What actually happened after you decided. The single most valuable thing you can send us, and the only way an assessment gets better at your book specifically.
2 endpoints ·
/v1/outcomes
POST/v1/outcomesreference
Submit Outcome
Report what happened after a decision (command SubmitOutcome). Feeds calibration (E14).
bodyOutcomeIn201ObservationOut
POST/v1/outcomes/batchreference
Submit Outcomes
Report many outcomes at once (a month of repayments, a day of chargebacks).
bodyOutcomeIn[]201ObservationOut[]
Material
Documents, images, audio and video, declared before they are sent. Extraction produces bindings; the bytes themselves can be processed and never stored.
5 endpoints ·
/v1/material
POST/v1/materialreference
Create Material
Declare material (command IngestMaterial).
A text material carries its text and is held at once; its id is the sha256 of the text, which is what
an inquiry names in material_ids. Anything else declares the sha256 of the bytes that will follow and
is told where to put them (PUT the bytes to upload_url). retention_mode is a promise (D35): the
default, transient, is released as soon as the inquiry that reads it concludes. Only text is read
today; an image or a document is stored and an inquiry that binds one is refused with that reason. C2
material is refused.
bodyMaterialCreate201MaterialOut
GET/v1/material/{material_id}reference
Get Material
The material's status. A material that is not yours is not found.
200MaterialOut
Parameters
material_id
path
required
DELETE/v1/material/{material_id}reference
Delete Material
Let go of the content now. The record that it was held, and for what, stays.
204no body
Parameters
material_id
path
required
PUT/v1/material/{material_id}/contentreference
Put Material Content
The bytes of a declared material. They must hash to material_id.
200MaterialOut
Parameters
material_id
path
required
GET/v1/material/{material_id}/extractionreference
Get Extraction
What is stored about the material's extraction; what a message named is in the inquiry's findings.
200ExtractionOut
Parameters
material_id
path
required
Cases
An investigation with more than one subject, more than one analyst, and a record of who did what. For investigative tenants; every case carries an authorisation.
14 endpoints ·
/v1/cases
POST/v1/casesreference
Open Case
Open a case (command OpenCase).
Requires an investigative tenant (KYB) and an authorization record (I13).
bodyCaseCreate201CaseOut
GET/v1/cases/{case_id}reference
Get Case
The case and its current state, derived from its event log.
200CaseOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/assertionsreference
Assert In Case
An analyst's judgement as evidence (command AssertInCase, E9).
bodyCaseAssertionIn201ObservationOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/closereference
Close Case
Close the case (command CloseCase).
200CaseOut
Parameters
case_id
path
required
finding
query
optional
GET/v1/cases/{case_id}/eventsreference
Case Events
SSE: CaseChanged, AssessmentRevised for expansions, MonitorTriggered for case monitors.
200no body
Parameters
case_id
path
required
after
query
optional
POST/v1/cases/{case_id}/expandreference
Expand Case
One hop of attribution (command ExpandCase), budgeted.
With human_gate the candidates are shown first and nothing is spent until one is chosen.
bodyCaseExpandIn202InquiryResponse
Parameters
case_id
path
required
POST/v1/cases/{case_id}/exportreference
Export Case
Produce the evidentiary bundle (command ExportCase). Requires sign-off.
202CaseExportOut
Parameters
case_id
path
required
format
query
optional
GET/v1/cases/{case_id}/graphreference
Case Graph
The case graph: nodes and edges with types, weights and provenance classes.
200CaseGraphOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/holdreference
Hold Case
Place legal hold (command HoldCase).
bodyCaseHoldIn200CaseOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/intakereference
Intake Case
Bring many things into a case at once (command IntakeBatch, D43).
A bounded manifest of presentations and declared material; bytes follow by
hash. Each item answers for itself (accepted, duplicate, rejected); the
manifest becomes one case event. Nothing is spent: gathering is expand.
For open-ended intake open a session with case_id instead.
bodyIntakeManifest201IntakeOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/membersreference
Add Case Members
Add members (command AddCaseMembers).
bodyCaseMemberIn200CaseOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/releasereference
Release Case
Release legal hold (command ReleaseCase).
bodyCaseHoldIn200CaseOut
Parameters
case_id
path
required
POST/v1/cases/{case_id}/reviewreference
Review Case
Move the review state (command ReviewCase).
bodyCaseReviewIn200CaseOut
Parameters
case_id
path
required
GET/v1/cases/{case_id}/timelinereference
Case Timeline
Everything that happened in the case, in observed order.
200EventEnvelope[]
Parameters
case_id
path
required
Monitors
A standing watch on a subject. You are told when the answer changes, rather than asking again on a schedule.
4 endpoints ·
/v1/monitors
POST/v1/monitorsreference
Open Monitor
A standing watch (command OpenMonitor).
bodyMonitorCreate201MonitorOut
GET/v1/monitors/{monitor_id}reference
Get Monitor
The monitor and its last assessment.
200MonitorOut
Parameters
monitor_id
path
required
DELETE/v1/monitors/{monitor_id}reference
Close Monitor
End the watch (command CloseMonitor).
204no body
Parameters
monitor_id
path
required
GET/v1/monitors/{monitor_id}/eventsreference
Monitor Events
SSE: MonitorTriggered.
200no body
Parameters
monitor_id
path
required
after
query
optional
Sessions
A live connection for open-ended intake: frames in, events out, over a WebSocket.
2 endpoints ·
/v1/sessions
POST/v1/sessionsreference
Open Session
Open a live session (command OpenSession); returns the WebSocket URL for frames and events.
bodySessionOpen201SessionOut
POST/v1/sessions/{session_id}/closereference
Close Session
Close a session (command CloseSession); the retention mode is applied.
202no body
Parameters
session_id
path
required
reason
query
optional
Entities
A subject we have resolved across more than one identifier, and its assessments in order, which is reputation over time.
2 endpoints ·
/v1/entities
GET/v1/entities/{entity_id}reference
Get Entity
A resolved subject as the tenant may see it.
200EntityOut
Parameters
entity_id
path
required
GET/v1/entities/{entity_id}/ledgerreference
Get Ledger
The entity's assessments in order: reputation over time.
200LedgerEntryOut[]
Parameters
entity_id
path
required
Registry
What your tenant may present, ask and declare. Read it at startup rather than hard-coding a list that will drift.
3 endpoints ·
/v1/registry
GET/v1/registry/artifact-typesreference
Artifact Types
Artifact types this tenant may present, from the loaded packs, with the platform list for a handle.
200RegistryEntryOut[]
GET/v1/registry/intentsreference
Intents
Intents this tenant may use.
200RegistryEntryOut[]
GET/v1/registry/purposesreference
Purposes
Purposes this tenant's policy allows.
200RegistryEntryOut[]
Control plane
Keys, policy, webhooks and your audit trail. Separate scope; a key that can open inquiries cannot mint another key.
8 endpoints ·
/v1/admin
GET/v1/admin/auditreference
Audit
The tenant's audit trail: every call and analyst action with its cost.
200AuditEntryOut[]
Parameters
after
query
optional
limit
query
optional
POST/v1/admin/keysreference
Mint Key
Mint a key (command MintKey): shown once, stored hashed (I11).
bodyKeyCreate201KeyOut
GET/v1/admin/policiesreference
List Policies
Every policy version this tenant has published, current first.
200PolicyOut[]
POST/v1/admin/policiesreference
Publish Policy
Publish a policy version (command PublishPolicy). Labels change; scores never do.
Empty bands means the loaded packs' default bands. The new version is the tenant's current one; the
versions before it stay, because an assessment already labelled names the version that labelled it.
bodyPolicyIn201PolicyOut
POST/v1/admin/trialsreference
Provision Trial
Provision an X-Ray trial for one address and return its key, once.
The only route that mints a credential for somebody who is not in the
room, so three things bound it and all three are here rather than in the
caller. It needs the trials scope, which one key in one deployment
holds. It takes one field, so nothing about the trial's shape can be asked
for. And every value it writes — tier, budget, limits, purposes, lifetime
— is a constant in control.trials, which means a stolen provisioning key
can create trials and cannot create anything better than a trial.
Whoever may hold a trial is decided before this is called, by the
whitelist in the surface that calls it. This route deliberately does not
know that list: it is a policy about people, it changes often, and putting
it here would make every change to it a deploy of the gateway.
bodyTrialCreate201TrialOut
POST/v1/admin/webhooksreference
Register Webhook
Register a webhook (command RegisterWebhook).
bodyWebhookIn201WebhookOut
DELETE/v1/admin/keys/{key_id}reference
Revoke Key
Revoke a key (command RevokeKey).
204no body
Parameters
key_id
path
required
GET/v1/admin/trials/{tenant_id}/usagereference
Trial Usage
What one trial has left: calls today, budget spent, days remaining.
Read by the playground to draw its own usage strip, so the numbers a
prospect sees are the numbers the gateway is actually enforcing rather
than a second count kept by the page and drifting from it.
200TrialUsageOut
Parameters
tenant_id
path
required
Health
Liveness, for your monitoring. `/healthz` additionally reports the running build, the tool count and whether the service can reach its own database.
2 endpoints ·
/v1/health
GET/healthzlive
Healthz
Liveness and the two things worth knowing before a deploy is believed.
Open, like the provider service's own health endpoint: it reveals how
many tools were discovered and whether the gateway's schema answers,
and nothing about any tenant.
200no body
GET/v1/healthlive
Health
Liveness. The only endpoint with a body today.
200no body
Objects
The shapes you send and receive. Every one is closed: an unrecognised field is an
error rather than something silently ignored.
InquiryRequestAsk about a subject at a stake, for a purpose, with an intent
subjectrequired
Subject
intentrequired
string
A registered intent id, e.g. pre_transaction, onboarding_screen.
purposerequired
string
A registered purpose id. Required on every call (I13).
stakerequired
Stake
fraud_intake
FraudIntakeV1
context
ObservationIn[]
The caller's own testimony, attached inline: at most 20, each about something this inquiry presents, each under this inquiry's purpose, and tenant_supplied or self_attested (with a consent reference). It is written into the inquiry's evidence as the caller's word and never lends a tool's trust. A subject's name is carried as an observation whose summary is Name: <text>.
material_ids
string[]
Bound supported text material; images/PDF/OCR are not readable evidence. Binding unreadable or mixed text/non-text materials is refused. Declaration/storage alone does not run a check.
consent_ref
string
The caller's own record of the reader's consent, for example the id of the consent event. Required for a purpose that enumerates someone's own accounts (self_exposure_audit); otherwise optional. It is an opaque reference, never the consent text.
tier_ceiling
string
Highest provider tier this inquiry may use.
render
"none" | "template" | "model"
Whether to write the findings up as a report. none is the default because a caller that only wants the numbers should not pay for prose. A tenant may be clamped below what it asks for; the reply says which renderer ran.
render_lang
string
Language tag for the report, e.g. en, hi.
mode
"sync" | "async" | "stream"
idempotency_key
string
SubjectWhat the inquiry is about: presentations, an entity we already know, or a claim
presentations
Presentation[]
entity_id
string
A subject we have resolved before.
claim
Claim
PresentationOne presented identifier: a registered artifact type and its value
typerequired
string
A registered artifact type id (see GET /v1/registry/artifact-types).
valuerequired
string
The presented value; normalised by the kernel.
StakeWhat is at risk and how much time there is; fixes the tolerable interval and the budget
AssessmentThe public projection of a kernel Assessment
assessment_idrequired
string
inquiry_idrequired
string
scorerequired
integer
lowrequired
integer
highrequired
integer
preliminaryrequired
boolean
True when the stopping rule was not yet met (pre_transaction only).
as_ofrequired
string
methodology_versionrequired
string
labelrequired
Label
evidencerequired
EvidenceSummary
entity_idrequired
string
EvidenceSummaryWhat the tenant may see of the chain of evidence: counts and bands, never raw or provider names
signalsrequired
integer
failed_signalsrequired
integer
contradictionsrequired
integer
by_provenance_classrequired
object
by_trust_bandrequired
object
oldest_observed_atrequired
string
newest_observed_atrequired
string
FindingOne thing that was established about the subject
finding_idrequired
string
node_id
string
The node in graph this fact is about, when the check drew one. Opaque and stable within this response only.
aboutrequired
string
The caller's own presented value this concerns, when it was theirs.
about_typerequired
string
The registered artifact type of about.
kind
string
What sort of check produced this, e.g. account_age, domain_popularity. A renderer uses it to say what a finding of this sort means; it names the question asked, never who was asked.
statementrequired
string
What was found, in words, with every source name removed.
disposition
"supports" | "weakens" | "neutral"
Which way this points for somebody deciding whether to trust the subject, as the source itself declared it. Never parsed from statement, never a score, and never an input to the assessment. It is here so a tenant's policy can form a label (D05).
provenance_classrequired
string
How this came to be known, e.g. third_party, computed.
trust_bandrequired
"high" | "medium" | "low"
The banded trust of its source.
observed_atrequired
string
data_classrequired
string
C0, C1 or C2. What handling this fact requires.
attributes
object
What the source said, as structure, when it said something that has one. For a statement a public page makes: predicate (role, affiliation, founded, located, event, ownership, dispute, description, public_statement, review), quote (the page's own words, verbatim), source_url and page_date. For a profile: the platform, name, bio, location and when the account was created. Absent for most findings. It is what was said, never what it is worth.
ConnectionAn edge the engine drew between two things, and why it drew it
How the edge came to exist, so a reader can weigh it: declared (a source reported it), resolved (evidence says these are one subject), contradiction (two sources disagree), temporal (a date a source asserted), shared (both reach the same third thing), similar (their values are close), asserted (a person said so).
relationrequired
string
The registered relationship type, e.g. shares_registrant.
from_labelrequired
string
The caller's own value where it was theirs, else its type.
from_typerequired
string
to_labelrequired
string
to_typerequired
string
weightrequired
number
The kernel's computed strength for this edge.
reasonrequired
string
Why the edge holds, with every source name removed.
ReportOne inquiry, written for the person who asked
inquiry_idrequired
string
assessment_idrequired
string
lang
string
rendered_byrequired
"template" | "model"
Which renderer produced this. A consumer should not otherwise be able to tell.
prompt_version
string
The prompt that wrote it, when a model did. Null for a template.
depth
ReportDepth
How deep the report went and what a deeper one adds. Set on the individual report.
sectionsrequired
ReportSection[]
template_sections
string[]
Sections the template wrote because the model's did not survive its checks (a paragraph citing something it was never given, a section that did not validate, or one it left out). Empty for a report the model wrote whole and for a template report.
sharerequired
ShareCardOut
generated_atrequired
string
ObservationInTestimony the caller supplies about a subject, entering with its provenance class
A refusal is an answer, and it names the rule that produced it. Every call, refused
or not, writes one audit row whose id comes back on X-Griffynx-Audit-Id.
Status
Means
What to do
200
Concluded, with an assessment.
Read the interval.
401
No key, or a revoked one.
Check the bearer token.
422
Refused. The body names the rule.
Do not retry unchanged. A refusal for purpose or intent means your tenant is not
permitted to ask that, and asking again will be refused identically.
501
A published contract with no handler yet.
The shape is fixed; build against it and it will start answering.
502
The engine could not complete.
Retry once. The body carries the audit id for the attempt.
Versioning and deployment status
The reference is generated from a named source contract. It is not deployment evidence. Read /healthz for the revision and its JSON status: HTTP 200 alone can still mean degraded.
Collection wire 2.0.0 remains compatible. The additive semantic vocabulary is 1.0.0 in SDK 2.1.0. Kernel a25 and report-core 1.0.0rc2 form the candidate core. Historical /v1 methodology remains separately versioned.
Unknown source rights, unsupported capabilities and pending independent human acceptance remain explicit release gates.