Let the bloggers in the directory sell what the crawlers are taking

[ralyodio]

The directory is other people's blogs. traffic_hourly says most of what reads them is machines, and crawl_sales now says what those machines paid. None of that money had any route back to the people who wrote the posts.

/sell is that route.

What a publisher walks through

1. The pitch at /sell, public, with the ladder and what they need.
2. Prove they own the site behind a feed we already index. A DNS TXT record or one file under /.well-known, both automated; there is no "email us" path.
3. Pick topics from the directory's own busiest 40, resolved per request so a topic that appeared this week is claimable this week.
4. Add a USDC address.
5. Get paid a share of what crawlers pay.

The rate starts at 20% and climbs 5 points per verified property and per niche to 80%, on the same commissionLadder the public board displays.

Attribution

Only this side knows whose feeds are in the index, so the split lives here: a verified domain is matched against the host of each feed's site_url, and a sale is shared pro-rata by items contributed, each partner at their own rate.

The credit ref carries the partner id, so a settlement delivered twice pays once. The split runs after the sale is booked and can never fail it, because the money has already moved.

Two decisions worth reviewing

• A missing secret 404s /sell instead of crashing the site. The module will not construct without PARTNER_VERIFY_SECRET, which is right (a guessable verification token pays the wrong person for someone else's writing), but that must not take the directory down on a deploy where the variable was forgotten.
• The pitch is in OPEN_PATHS. Charging a crawler to read our own recruiting page would be an odd way to run a marketplace. The data itself stays paywalled.

Verified against a local libSQL file, driving the real route handler

• signed out: the pitch renders with a call to action; the dashboard redirects to /signin?next=/sell
• apply lands on the dashboard; a property shows its real verification token
• one verified property plus two topics reads 35%
• a $20 sale splits to 700 cents; the same sale replayed adds nothing
• the existing 382 tests still pass, and the build carries /sell/[[...path]]

PARTNER_VERIFY_SECRET is already set on the rssamplifier.com service and stored in the rssamplifier-com--prod vault.

🤖 Generated with Claude Code

https://claude.ai/code/session_0144uEVbZK3jdaQkwcLYTXPE

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​profullstack/​partners@​0.2.0

View full report