Skip to content
Live Network

Four engines.
One network.
Three faces.

Daily voice, SERP gap-hunter, 14-day forecast, cross-industry Oracle. One API powers all of them across networkr.dev, viralr.dev, and outboxr.dev. Same brain. Three distribution surfaces. One connection unlocks all of it.

The Four Engines

Every site plugs into the same intelligence

V1 writes about today. V2 finds what nobody else is covering. V3 forecasts what your audience asks in two weeks. V4 sees how a story in one industry ripples into the next four. Same engine, different sight ranges.

V1·LIVE·Voice

What's happening today, in your voice.

Daily news from your industry wrapped in your tone, your angle, your build-log story. You stay top of mind and top of search without writing a word. Same story, in your voice — not another AI slop feed.

V2·LIVE·Gap Hunter

The content nobody else wrote.

Scans the SERP, finds queries with fewer than five real competitors, and owns them by default. While everyone else fights for the same crowded keywords, you take the empty ones — and Google has no choice but to rank you.

V3·BEARING FRUIT·Forecast

Publish the answer before the question exists.

We signal-converge across news, SERP, and industry chatter to forecast what your audience will ask in 14-30 days. You publish the answer today. When the story breaks and the search surge hits, you're already indexed and ranking — two weeks before anyone else even sees it coming.

Receipt

Eleven days before Wikipedia banned AI-generated content, V3 forecast the query “why Wikipedia removed all AI rewritten articles entirely.” When the story broke, we were already indexed on it.

Backtested across AI-SEO, cybersecurity, and fintech regulation: 20-30% exact hit rate, 45-67% topic-matched at an 11-day horizon. Same engine, three vocabularies, no per-industry tuning.

V4·ROADMAP·Oracle

See chain reactions across industries, not within them.

When a story breaks in one industry, Oracle traces how it ripples into the next four — Wikipedia AI ban → university citation policies → AI-liability insurance → verified-human imprints → content strategy. Five industries, one chain, indexed across all of them before anyone else sees the connection. Only possible because the network sees every industry at once.

Status definitions: LIVE— shipping posts on networkr.dev right now. BEARING FRUIT— backtest-validated across multiple industries, live publishing rolling out. ROADMAP— spec locked, builds after V3 generalizes at scale.

Three Faces, One Engine

Same brain. Three distribution surfaces.

The intelligence that forecasts what your audience will search is the same intelligence that writes your newsletter and the same intelligence that drafts your social posts. One connection. Three faces. Zero duplicated effort.

networkr.devLIVE
SEO Content Engine

The blog surface. Forecasted, gap-hunting, voice-matched articles that rank on Google before the trend arrives. This is where V1-V4 write.

viralr.devSOON
Social Distribution

The social surface. Same intelligence, reshaped for organic social and paid ads. When V3 forecasts a question, viralr.dev shapes it into threads, posts, and ad hooks before the crowd shows up.

outboxr.devSOON
Email Orchestration

The inbox surface. Sends through your own list infrastructure, zero PII default. When V3 predicts the question, your newsletter subscribers get the answer in their inbox the same morning you publish the post.

What “same API” actually means

One industry research pool. The forecast that fires on networkr.dev fires on viralr.dev and outboxr.dev the same hour.
One voice + author config. Your tone, your byline, your brand mark — consistent across blog, social, and email.
One quality gate. The same guardrails, fact-checks, and approval layer apply to every surface. Nothing ships without passing the same review.
One connection to manage. Install once with npx networkr install. Every new surface we add lights up automatically for every existing tenant.
Authority Ladder

Sites are matched by domain authority

Cross-links only flow between sites in the same DA band or one band apart. A DA 5 site gets links from sites up to DA 30. When it grows to DA 20, it unlocks links from DA 50. Authority builds in steps, not jumps — the way Google expects it.

Band E
DA 75+
Band D
DA 50–75
Band C
DA 30–50
Band B
DA 15–30
Band A
DA 0–15

The Link Ladder

Lower DA sites receive links from one band above — pulling them up. Mid-band sites receive from one above them. Authority flows naturally through the network like a chain lift. No site jumps from DA 10 to getting links from DA 70 — that would trigger every spam filter Google has. The ladder prevents it by design.

Network Safety

The network protects itself

Every site in the network affects every other site. One bad actor could poison the entire graph. So the system watches, detects, and acts automatically.

Scam Detection

Sites are monitored for spam patterns, thin content, redirect chains, and deceptive practices. Automated scans flag suspicious behavior before it can affect the network.

Auto-Removal

When a site gets flagged, all cross-links pointing to it are automatically removed and replaced with links to the next highest-scoring relevant article. The network heals itself.

DA Band Enforcement

Cross-links are restricted to adjacent DA bands. A DA 10 site never gets a link from a DA 70 site. This prevents the unnatural link patterns that get networks penalized.

Domain Verification

Sites must verify domain ownership before network features activate. DNS TXT record or meta tag verification. No anonymous domains.

Anti-Fingerprint

Publish times randomized within 4-hour windows. Article lengths vary 1,200–3,500 words. Cross-link counts vary 1–5 per article. No two sites in a network share a detectable pattern.

Relevance Threshold

Every cross-link must exceed a minimum relevance score (tag overlap + keyword matching + recency). No random links.

Network Rules

Play fair or get out

The network is only as strong as its weakest link. One bad actor can poison the authority graph for everyone. So the system has zero tolerance. It watches, it detects, and it acts — instantly and without warning.

What gets you removed

×Spam content, thin pages, or AI-generated bloat with zero editorial value
×Redirect chains, cloaking, hidden text, or keyword stuffing
×Scraped or plagiarized content from other sites
×Any attempt to manipulate cross-link scoring or DA reporting
×Malware, phishing, scam activity, or deceptive practices of any kind
×Domains that bring negative SEO signals into the network — toxic backlinks, manual penalties, or Google sanctions

What happens when you're flagged

1.All cross-links pointing to your site are removed from every article in the network — instantly
2.Those links are replaced with the next highest-scoring relevant article. The network heals itself.
3.Your site is disconnected from Networkr. Pipeline stops. Network access revoked.
4.Your domain is blacklisted from reconnecting. There is no appeal process for scam or malware violations.
5.The network continues as if you were never there.

What playing by the rules earns you

Higher trust score — priority placement in cross-link selection across the network
Faster DA band progression — consistent quality content accelerates your climb up the ladder
Tenure bonus — long-standing network members receive a weighted boost in relevance scoring
Network uplift — as your authority rises, every site linked to yours rises with it. You don't just grow — you lift the network.
Protected investment — the scam detection, spam filtering, and instant removal systems exist to protect your authority from bad neighbors

The safety systems aren't here to be restrictive. They exist so that when you invest in the network, your investment is protected. Every bad site removed makes your site stronger. Every clean site that joins makes the network more valuable for everyone.

For AI Agents

Built for machines, not just humans

Networkr is API-first. No browser needed, no dashboard to scrape. AI agents and automation pipelines connect sites, trigger generation, and monitor the network with plain HTTP calls — no servers to install, no protocol clients to configure.

agent — start the install rail
// Any agent that can make HTTP requests drives this rail

POST https://api.networkr.dev/api/install

{
  "domain": "client-site.com",
  "email": "client@company.com"
}

// Returns install_token + first next_step envelope.
// Loop: POST /api/install/<token>/step until done.
// Full envelope schema: networkr.dev/brief.md
agent — monitor and generate
// Check network health
GET /api/orchestrator/latest

// Trigger article on demand
POST /api/sites/:id/blog/generate
{ "topic": "Edge computing trends 2026" }

// Get keyword rankings
GET /api/seo/keywords/:siteId

// Run SEO Brain for topic discovery
POST /api/seo/brain/trigger
{ "site_id": "client-site-com" }

// Public stats (no auth)
GET /api/network/stats

Agent Integration Patterns

Repo-parked Agent— Drop .networkr/AGENT.md in your repo; your IDE agent (Claude Code, Cursor, Aider) reads the brief and handles setup, self-heal hooks, and weekly reporting. No server install.
Cron Agent— Let your agent check orchestrator reports and act on recommendations
Multi-Site Manager— Agent connects multiple client sites, monitors performance across portfolios
SEO Autopilot— Agent reads keyword rankings, triggers SEO Brain when gaps are detected, generates targeted content

Join the network

One command to connect. DA-matched cross-links. Automated protection. Free forever.