Assistant and internal tooling
Typed MCP responses support enterprise assistants and custom workflows without reducing the result to a score.
Enterprise delivery
Built to travel with the decision.
The index is consumed through typed responses, hiring-system attachments, and a console for the people who own legal and people risk.
Authorization, confidence, evidence state, permitted use, and refusal remain attached to every result.
Primary surface
Model Context Protocol makes the refusal machine readable.
An assistant, hiring system, or internal tool asks for a read and receives a typed response. Unknown cannot be quietly rounded into zero.
A downstream system cannot read a hidden answer because no answer exists.
Request
Response
Receipt
toolplacement.read
engagement_ideng_9f2c41
subject_refsub_4498
purposeauthorized_hiring_read.v1
assessment_date2026-09-12
Typed response
The contract carries the limits with the answer.
A placement response includes its confidence band. A refusal carries confidence null next to level null. Permitted use appears on every response.
placement.read · typed response
{
"placement": "RECOGNIZED_CREDIBILITY",
"level": "Recognized Credibility",
"confidence": "High",
"score": null,
"sources_found": 18,
"sources_bound": 12,
"sources_not_read": 3,
"permitted_use": [
"authorized_hiring_read.v1"
],
"receipt": "rcpt_01K9...f12"
}Illustrative response with invented subject and source counts.
Three enterprise surfaces
One instrument, delivered where the risk is owned.
The interface may change by context. The contract and boundaries do not.
Hiring-system attachment
The read sits on the requisition with authorization, subject confirmation, and the permitted use carried on the record.
Governance console
Legal, compliance, and talent leadership review evidence state, authorization history, reinvestigation, and refusals.
What always travels with a placement
The result is not complete without the information required to interpret and govern it.
Placement level and confidence band together
Sources found, bound, and not read as separate counts
Evidence states and inspectability metadata
Permitted use and engagement authorization
Receipt and audit history
What always travels with a refusal
The absence of an answer is structured so a downstream system cannot invent one.
Level, confidence, and score returned as null
Refusal reason at the decision level
Source counts kept distinct
Permitted use returned as none
Receipt, timestamp, and auditability
Governed from the first call
Human review remains in the loop.
Employment use is authorized per engagement and disabled by default, and a documented compliance and reinvestigation process governs every read.
Enterprise engagement
Design the delivery around your hiring and governance stack.
Enterprise access begins with the use case, authorization model, and systems that will consume the result.