Provider adapter contract and current availability
GridZen adapters implement an async evaluate(request) operation returning normalized evidence. The alpha includes local-baseline and an optional, disabled-by-default Twilio Lookup adapter. Standalone provider preflight tools are separate from customer Decision API adapters.
Adapter inputs and outputs
Adapters receive the common DecisionRequest and return a list of Evidence. Required identifiers and permitted evidence depend on the exact upstream product. The registry rejects unknown IDs and, in pilot mode, rejects routes outside the account allowlist. Selecting a provider ID does not establish authorization or activate an account.
Twilio Lookup boundary
The current adapter requests line-type intelligence and returns phone validity and a reduced line-type class. Credentials come from deployment configuration. Controlled live evaluation requires an approved customer route. This adapter does not send SMS, perform subscriber-name matching or establish Mexico/Indonesia identity coverage.
New provider route checklist
Before enabling another route, verify product rights, credential ownership, required fields, timeout behavior, normalization and audit minimization. Test upstream success and failure using a transport mock, then a separately authorized sample. Didit and MaxMind preflight candidates are technical evaluation tools; do not advertise them as active managed packs.
Sources and scope
Based on the alpha contract and source implementation. Live route availability requires separate confirmation.