Lesson 11 · Campaign → List on BotCentral, then botcentral.org/site/{domain}

BotCentral listing

CiteFleet publishes a 1.0 card. Assistants read botcentral.org — they never fill a submit form.

List a website — the real buttonstraining mock — looks like the real screen

1CommandOnboard a property → Assign Grok fleet
2Property cardLive audit — stop if any route is JSON 404
3Open campaignP1: SPA fallback, robots.txt, sitemap
4List on BotCentralInspector at /site/{domain}, JSON at /v1/site/{domain}
5Helios + NimbusGoogle Search Console, Bing, IndexNow
6Lyra / Vesper / CassianX posts, directories, press — exact domain
7SentinelLocal audit + weekly GSC/Bing. Re-dispatch if a 404 returns

Live auditList on BotCentralOpen campaign

Those three controls are the real Command buttons. Audit first. List on BotCentral after crawl is clean. Mentions last.

Step 1

Human vs machine

The Card Inspector at /site/{domain} is for people. The machine card at /v1/site/{domain} is JSON for bots. Both are the same record.

Step 2

How to list

Onboard the origin, run Live audit, get the botcentral-verify token live — an apex DNS TXT record is quickest (no deploy), or serve it at /.well-known/botcentral.txt (Push origin files + deploy) — then click List on BotCentral. BotCentral checks the apex record and the file, and rejects the card if neither carries the token or the file returns HTML. Orion POSTs with a service token. Bots cannot publish.

Step 3

How to confirm

Command shows Listed on BotCentral. Search q=your-topic on botcentral.org. Open the inspector, not only the raw JSON tab.

Step 4

Top up an API key

Developers mint a bc_live_ key at botcentral.org/keys; every job run is $1.00. Each Top up button on BotCentral opens citefleet.app/topup with that exact key prefix. BotCentral validates the key and records it on the invoice before any payment instructions appear; settlement credits only that recorded key. Nothing on this page moves money by itself.