Report pipelines
Send public URLs or approved source lists, receive structured reports with source URL, fetch time, confidence, and raw JSON.
Developers and automation teams
Review-gated API and MCP access for public-web intelligence.
Use LumenRadar when a workflow needs source-backed reports, structured data, account-level credits, and an approval-controlled bridge into automation clients.
What developers can build
Agent workflows
Connect approved MCP clients to launch-safe tools so agents can request scans, extract fields, and route outputs into internal workflows.
Private intelligence memory
Request a custom brain for a narrow market, competitor set, source group, or recurring business-monitoring job.
Access model
1. Create account
Start with free credits and run the live public-data modules first.
2. Submit use case
Describe source types, volume, output format, compliance needs, and refresh frequency.
3. Review and quote
API/MCP access is approved by scope, not opened to every new user automatically.
4. Issue access
Approved accounts receive the access path, credit limits, and operating boundaries.
Public boundary
- Allowed: public pages, authorized sources, customer-provided URLs, source-backed reports, compliance-aware monitoring.
- Reviewed: high-volume runs, API/MCP keys, custom brains, recurring industry monitoring, paid data providers.
- Not self-service: private accounts, restricted systems, unauthorized login-only data, or workflows that depend on bypass marketing.
GitHub traffic plan
LumenRadar can later publish small developer-facing examples without exposing the production source code: JSON report examples, MCP client setup notes, schema samples, and safe demo workflows. This gives GitHub search traffic a clear path back to the product while keeping the core system private.
No production keys, internal source code, customer data, or private bypass modules should be published in GitHub demo material.