Offendersearch
AI integration

Safety checks for agents & chatbots

Give any LLM a reliable sex-offender screening tool. Define one tool call — or connect the MCP server — and your agent can search all 57 registries and cite official sources.

One tool definition

Drop this tool schema into your agent framework. The handler calls POST /v1/search; the model gets back scored, source-tagged records.

  • Works with any tool-calling model
  • Or skip the glue code with the MCP server
  • Verifiable results the agent can cite
{
  "name": "search_sex_offender_registry",
  "description": "Search US sex-offender registries by name, DOB, or location.",
  "input_schema": {
    "type": "object",
    "properties": {
      "firstName": { "type": "string" },
      "lastName":  { "type": "string" },
      "dob":       { "type": "string", "format": "date" },
      "state":     { "type": "string" }
    },
    "required": ["lastName"]
  }
}

AI integration FAQ

How do I give an LLM access to registry data?

Define a tool that calls POST /v1/search and hand it to your model, or connect the Offendersearch MCP server so the tool is available automatically. The model receives scored, source-tagged records it can cite.

Can I build a safety-alert workflow?

Yes. Re-run searches on a Weekly or Daily freshness tier and have your agent flag new matches — a common pattern for trust & safety and continuous monitoring.

Does the model see reliable, verifiable data?

Every record includes a confidence score, the match basis, and a link back to the official registry record, so agents can present verifiable answers rather than guesses.