External intelligence first · Paid agent access
Give your AI the commercial roofing intelligence layer.
Connect an approved AI workspace to the commercial roofing environment around your company: market signals, manufacturers, regulations, materials, labor, public opportunities and the published Tie-In record. Private contractor context is optional, read only and never pooled into shared intelligence by default.
What it does
Answers operators can act on.
RAN does the monitoring work. It normalizes official sources, preserves revision history, connects change across the industry record and applies the operator’s approved priorities—without requiring a contractor to reconstruct its operating system inside RAN.
What changed?
Compare canonical source snapshots, detect revisions and material movement, and distinguish corroboration from contradiction.
Why does it matter to us?
Rank evidence against the organization’s territory, watchlist and approved learning profile—without silently changing policy.
What stays private?
Contractor context personalizes relevance. It does not enter shared learning, benchmarking or a collective product unless a separate contribution agreement defines permission and value exchange.
Access flow
Five steps. Human control stays intact.
The agent can investigate and retrieve. It cannot approve a brief, change a project, rewrite a decision or expand its own access.
Activate
RAN approves the organization and enables the paid MCP entitlement.
Issue
An authorized operator creates a dedicated token in Agent Access.
Connect
Add the RAN endpoint and bearer token to a compatible MCP client.
Investigate
The agent retrieves scoped evidence, sources, changes and decision history.
Approve
People review actions and publisher outputs inside the Operator Desk.
Reference account
Proven with Division 7.
Division 7 is the founding operator reference account: one Central Ohio territory, a named watchlist, source-backed change detection, Friday delivery and a learning loop that improves relevance from real operator feedback.
The working loop
Evidence → review → decision → outcome → better watchlist.
Signals can be marked useful, irrelevant, false positive, monitoring or actioned. Owners and deadlines are recorded. Approved outcomes become durable receipts and inform future briefs.
33Named watch items configured for the founding territory.
0Filler items required. If the evidence is not relevant enough, the publisher does not manufacture a brief.
100%Human approval required before a publisher output becomes an approved delivery.
Useful on day one
Ask the record, not the open web.
An MCP client can combine these questions with its own reasoning while RAN supplies the controlled evidence layer.
What changed this week that could affect a commercial roofing contractor in Central Ohio?
Which manufacturers changed instructions, approvals, availability or lead-time guidance? Show the source and date.
Which owners or properties in our territory are showing multiple capital-event signals?
Where are labor, material or freight conditions creating new margin pressure?
What are experienced operators saying about this system or installation problem, and where do they disagree?
Which current signals connect to something RAN observed six months ago?
Connect
One secure endpoint.
Use remote HTTP MCP in a compatible client. Create a separate token for each AI workspace so access can be expired or revoked independently.
https://www.roofingauthority.network/api/mcp
{
"mcpServers": {
"ran-intelligence": {
"type": "http",
"url": "https://www.roofingauthority.network/api/mcp",
"headers": {
"Authorization": "Bearer ran_mcp_YOUR_TOKEN"
}
}
}
}Configuration keys vary by client. Never paste a token into a public prompt, shared document or source repository. The token is shown once when created and stored hashed by RAN.
Current surface · v1.2.0
13 core tools. 24 permissioned tools.
The external core is useful without private contractor data. Organization relevance and advanced contractor intelligence remain permissioned layers; every response preserves uncertainty, provenance and access scope.
Advanced pilot · Project evidence
list_projects · get_project
search_project_documents
get_document_revision · list_findings
get_finding_evidence · compare_revisions
Industry record
list_episodes · search_episode_transcripts
get_transcript_passage · trace_quote
ask_network · get_topic_dossier
compare_speaker_perspectives
Market context
search_industry_signals
get_signal_sources
get_signal_context
Decision memory + relevance
list_intelligence_decisions
get_intelligence_decision_receipt
get_intelligence_learning_profile
list_intelligence_learning_changes
Change Publisher v2
list_intelligence_changes
get_intelligence_change
get_intelligence_publisher_output
Advanced pilot · Roof ID
list_roofs · get_roof
get_roof_evidence
list_roof_unknowns
Explicit opt-in · Private context
list_private_context_sources
search_private_context_records
get_private_context_record
list_private_context_access_events
Advanced pilot · Bid Truth
list_bid_truth_opportunities
get_bid_truth_opportunity · get_bid_truth_assessment
list_bid_truth_evidence_gaps
get_bid_truth_decision_receipt
Paid boundary
pilot · trialing · active
Requires mcp_read_only
Inactive subscriptions are rejected.
Trust contract
Useful access. Narrow authority.
MCP is the paid delivery surface over the RAN Evidence Graph. Official sources remain official. RAN sells the work of finding, normalizing, versioning, ranking and connecting that evidence to an operator’s real decisions.
Tenant + grant bound
Private results require the token’s organization, an approved field-level grant and—when private context is requested—an opted-in token scope.
Source attached
Document locators, transcript timestamps, publisher URLs and evidence hashes travel with results.
Read only
The agent cannot approve, edit or delete projects, grants, feedback, decisions, policies or publisher records.
No silent pooling
Private contractor content is not reused for shared learning or cross-contractor benchmarking by default. Any contribution requires a separate agreement and defined value exchange.
Questions
What paid access means.
The distinction matters: RAN does not charge for ownership of public facts. It charges for an accountable intelligence system built around them.
Is the MCP public?
The endpoint and tool schemas are discoverable. Every private evidence call requires a valid tenant-bound token and an active paid entitlement.
What are we paying for?
Normalized and versioned evidence, operator-specific relevance, decision history, managed delivery and a secure agent-access layer. Customers are not charged for ownership of their source-system data.
Can the agent take action?
No. The MCP retrieves evidence only. Approval, ownership, deadlines, outcomes, access grants and publisher decisions remain inside the Desk.
Does our private data improve RAN for everyone?
No—not by default. Private content stays tenant-bound and is excluded from shared learning and cross-contractor benchmarking unless a separate contribution agreement says otherwise. Read the RAN Data Compact.
RAN Intelligence MCP
Make the agent show its work.
Start with the industry intelligence RAN maintains, then add only the company context needed to decide what matters to you.