---
name: regulus-regulatory-research
description: Research United States pipeline and hazardous-materials regulatory questions using Regulus. Use when a task needs regulations, PHMSA guidance or interpretations, inspections, enforcement, incidents, NTSB records, rulemaking, state pipeline-safety sources, document relationships, historical context, or evidence-backed citations.
---

# Regulus regulatory research

Use Regulus as a source-discovery and evidence-navigation system. Do not present search snippets as controlling authority.

## Access

1. Prefer the read-only Streamable HTTP MCP server at `https://regulus.evalyn.ai/mcp`.
2. If MCP is unavailable, read `https://regulus.evalyn.ai/llms.txt` and use the Markdown API documented at `https://regulus.evalyn.ai/api/llm`.
3. Use `https://regulus.evalyn.ai/openapi.json` when a structured API contract is more useful.

No authentication is required. Respect rate limits, cache identical results, avoid duplicate concurrent requests, and honor `429 Retry-After`.

## Workflow

1. Search for the question, citation, equipment, operator, or regulatory concept.
2. Retrieve the complete controlling document rather than relying on its excerpt.
3. Retrieve focused passages for the exact proposition being evaluated.
4. Inspect hierarchy to establish title, part, subpart, definitions, applicability, and sibling context.
5. Inspect related authorities for amendments, supersession, guidance, interpretations, inspections, enforcement application, rulemaking history, and incident evidence.
6. Compare effective dates and document status before describing a requirement as current.
7. Explain the reasoning chain, contrary evidence, assumptions, and unresolved uncertainty.

## Authority and citations

- Distinguish binding regulations and statutes from nonbinding guidance, FAQs, interpretations, advisory bulletins, inspection material, enforcement records, and incident evidence.
- Cite the official `source_url` for every material proposition.
- Include the Regulus `app_url` as a navigation link when available.
- Quote only the passage needed and preserve citation, date, status, agency, and provenance.
- Never infer a legal requirement solely from semantic similarity, a relationship edge, a generated summary, or a search excerpt.
- For consequential compliance decisions, state that qualified counsel or the regulator should confirm the conclusion.

## Useful fallback requests

```text
GET https://regulus.evalyn.ai/api/llm/search?q=SCADA+testing&limit=10
GET https://regulus.evalyn.ai/api/llm/document?identifier=49+CFR+192.631
GET https://regulus.evalyn.ai/api/llm/passages?identifier=49+CFR+192.631&q=testing
GET https://regulus.evalyn.ai/api/llm/related?identifier=49+CFR+192.631
GET https://regulus.evalyn.ai/api/llm/hierarchy?identifier=49+CFR+192.631
GET https://regulus.evalyn.ai/api/llm/status
```

Markdown is returned by default. Send `Accept: application/json` or append `format=json` for JSON.