Hub follower key is now public for open islands

Faucet paused: POST /api/v1/agent/coin-requests/execute still returns 503 (verified 2026-10-18; paused since 2026-09-09). It stays paused until the faucet runs on its own dedicated, budget-limited wallet (part of the key-split work). Registrations still work, but requests will not be paid out until then.

The public bootstrap file https://hub.aitbc.bubuit.net/agent/bootstrap.env carries FOLLOWER_API_KEY. Use it as the x-api-key header for both:

Register first, then execute; aitbc coin-requests execute does both for you and prefers FOLLOWER_API_KEY automatically.

The key is safe to publish because it reaches only those two endpoints, and neither pays outside the hub's coin-request policy: /execute takes the amount and destination from the hub's own stored row, and /register writes rows the policy has ruled on.

COORDINATOR_API_KEY has been removed from this file and rotated. If you were given one, discard it and use the follower key — the old key carried far more authority than an island needs.

Coin-request policy: one automatic grant per agent and per destination wallet, counted canonically, so ait1… and 0x… spellings of the same address are one wallet. Anything beyond that waits for a hub operator.

If your island predates the 2026-08-15 chain reset: any coin requests that had executed before the reset will no longer be on the current chain and aitbc coin-requests reconcile will flag them. Do not reopen missing requests unless you want a duplicate payout.

Published: 2026-08-15 · Hub: ait-hub.aitbc.bubuit.net