FlyBeacon

FlyBeacon is a growth operator agent for Web3 and tech projects - "Growth, with receipts." It's built to be used by other agents, not humans clicking through a dashboard: every capability is a pay-per-call API tool, gated by the x402 payment protocol, and the whole thing is registered as agent #4442 (ASP role) on the OKX.AI marketplace at X Layer (chain eip155:196).

What it actually does — 9 tools across 3 groups

Core campaign pipeline (each feeds the next):

• Project Growth Analysis ($1) — deep research on a project from its URL/description: personas, positioning angles, channel fit, honest risks, up to 2 competitor X handles

• 7-Day Campaign Planner ($3) — turns that analysis into a concrete 7-day plan with themes, actions, KPIs, and a tracked-link attribution plan

• Campaign Content Pack ($2) — writes 5 ready-to-post variants (X thread, short post, Discord message, Reddit post, reply hook) for one day of the plan

• Campaign Execution Report ($5) — branded PDF built from real logged clicks/conversions, not projections

X and narrative intelligence:

• X Presence Audit ($2) — live X audit of any handle (cadence, mix, engagement, gaps)

• X Narrative Pulse ($0.50) — is a narrative heating/stable/cooling on X right now, with fresh angles

• Narrative KOL Discovery ($3) — finds up to 25 real, evidence-backed independent creators for a narrative, flags affiliations and spam risk

• KOL Outreach Pack ($1) — personalized first-touch outreach drafts, one per KOL, grounded in their actual evidence

All-in-one:

• Full Growth Dossier ($10) — chains the entire pipeline into one branded PDF; runs as an async background job (queues, advances one step at a time, polls to done)

How it's built

• Next.js 14 app deployed on Vercel, TypeScript throughout

• Claude (Sonnet) handles analysis, planning, content, and outreach writing, with live web search on the analysis step

• Grok (xAI) handles anything needing live X search - presence audits, narrative pulse, KOL discovery - so nothing is cached follower counts or invented posts

• Supabase (Postgres + Storage) holds campaigns, referral links, click/conversion logs, tool-response cache, and the dossier job queue

• jsPDF generates every report/dossier as a real PDF, using a consistent brand system (butter/cream/ink/beacon-orange palette, Fraunces + Inter type)

• x402 (@okxweb3/x402-core, exact-payment EVM scheme) gates every paid route before it runs

• Also exposed as an MCP server (/api/mcp) with all 9 tools under snake_case names, for any MCP-compatible agent runtime

Business model

Pure pay-per-call, no subscription - priced for the agent economy where another agent pays FlyBeacon directly, not a human on a SaaS seat. Three ways to call it: direct HTTP+x402, MCP, or through OKX's task marketplace. Only the last one creates a reviewable transaction - direct calls pay fine but never generate a task-id, so there's nothing to leave feedback on. FlyBeacon's public docs (/docs) now steer buyers toward that reviewable path deliberately, since that's what builds real, visible reputation on OKX.

Public site

flybeacon-indol.vercel.app - homepage (pitch + tool teaser + OKX badge linking to the live listing), /tools (full product breakdown), /pricing (price table + value case), /docs (infra + how to call it, for both buyers and ASP builders), /report (real embedded sample PDFs for a fictional example project, showing exactly what a buyer gets).

Progress Detail:

1. Register ASP on OKX.AI, wire the x402 Payment SDK, one paid call on X Layer testnet

2. Build the remaining tool routes (plan, content pack, report)

3. jsPDF report template in brand colors

4. List on OKX.AI with 2–3 seeded sample reports

5. 90-second demo video, post with #okxai, submit form by July 16

How it actually went — 11 commits, roughly three phases

Phase 1 - scaffold and core pipeline (2bb08e9, 651f9ad, 066f9bc): the initial Next.js app, the first four tools (analyze_product, generate_campaign_plan, generate_content_pack, generate_execution_report), the jsPDF report builder in brand colors, the /r/:code attribution redirect system, and the landing page.

Phase 2 - payment + KOL tooling (1cae41a, 26aaba2, 637acad, 68dbbb6): wiring x402 across all six original tools, a dependency compat fix for x402-next on Next 14, a fix to return payment requirements in the 402 response body specifically so OKX's own listing verifier could read it (this came out of an actual OKX rejection tied to the payment gate), and later a significant upgrade to KOL discovery - raised the cap from 8 to 25, added engagement/affiliate/notable-engager signals so ambassadors get disclosed instead of silently excluded.

Phase 3 - this session, three new tools + full site + OKX listing work (e7cfd3a, a812c04, cb3c604, 9ca90da): built X Narrative Pulse, KOL Outreach Pack, and the Full Growth Dossier (the async 9-step job pipeline chaining the whole toolkit into one PDF), gave them MCP parity, then built out /tools, /pricing, /docs, and /report (with real embedded sample PDFs) to replace the old in-page anchors. Alongside the code: added all 3 services to the live OKX listing (agent #4442) via the onchainos CLI's full update/QA/confirm flow, hit and worked around a binary checksum-mismatch twice, fixed a real PDF layout bug (panel heights miscalculated, causing text overlap on five different report sections), caught a .gitattributes gap that would have let git corrupt the sample PDFs, and figured out - the hard way, by watching the listing flip back to "under review" - that OKX resets the entire agent's visibility on any service change, not just the changed service, plus the actual mechanism for how reviews/reputation get earned (task-marketplace only, not raw pay-per-call).