Linear one-step chain checking NAIC producer license reciprocity for non-resident filing. Accepts resident state and target states (2-letter codes) plus standard NAIC LOA codes. Identifies non-standard states — CA, FL, NJ, NY, HI, MN, WI — that require independent filing, background checks, or state examinations outside the standard reciprocity path. Per NAIC Producer Licensing Model Act (MDL-218) and NIPR Reciprocity Matrix 2024. State codes and LOA enum inputs only — zero PII.
check_producer_license_reciprocity{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_producer_license_reciprocity",
"arguments": {
"resident_state": "OR",
"loa_codes": ["L", "H", "A"],
"target_states": ["TX", "IL", "CO", "NY"]
}
},
"id": 1
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: Our agent is licensed in Oregon. Can she add non-resident lines in her target states without sitting new exams?
Run the AINumbers MCP tool `run_chain` with {"chain":"producer-license-reciprocity"} and read `art-267-check-producer-license-reciprocity.all_reciprocal`.
Re-run with `inputs` for `art-267-check-producer-license-reciprocity`, reusing the values that result echoed, with `resident_state` set to "NY". Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/producer-license-reciprocity.html