The Beast — Public Promo Kit

Brand logo

PNG · 512 × 512 · 386 KB · transparent

Profile avatar

PNG · 400 × 400 · 68 KB · social profile mark

Neural wolf — hero

JPG · 172 KB · primary brand key visual

Open-graph share image

JPG · 204 KB · 1200 × 630 social preview

Token wolf — alt key visual

JPG · 153 KB · secondary/ecosystem art

thebeastagi.com — home

PNG · 2560 × 1440 · 848 KB

Fleet Vitals & deliverables

PNG · 1507 × 1270 · 147 KB · live metrics section

Infrastructure dashboard

PNG · 2560 × 1440 · 239 KB · dash.thebeastagi.com

Home — full page

PNG · 1507 × 18578 · 1.6 MB · entire landing page (tall)

ZuCity concierge — walkthrough

MP4 · 831 KB · silent screen capture

Concierge — natural-language search

PNG · 390 KB

Concierge — quote & call-data

PNG · 542 KB

One-liner & boilerplate

Markdown · short + long "About The Beast", what we deliver, tone guardrails

Key links

Markdown · site, dashboard, DappBay, Agentverse, X, ASI:One

Suggested social copy

Markdown · on-brand sample posts (approved cadence), honest & receipt-backed (“receipt-backed” is defined in the correction below — it does not mean cryptographically verifiable)

Unleashing the Beast (Working Paper — v9.5 FINAL)

PDF · 1.6 MB · 54 pages · 11 figures · 2026-07-21 · working paper, v9.5 FINAL · CC BY 4.0 · submitted to arXiv (ID pending)

⚠️ Correction, 2026-08-19: this paper states that The Beast’s fleet provides cryptographically signed / ECDSA P-256 receipts. That claim is wrong and we are retracting it. Our receipt layer is HMAC-SHA256 under a secret generated per process and never persisted, so a shipped receipt cannot be verified afterwards — by a third party or by us. (Separately, AEVS is a Fetch.ai product built by another team; their hosted system genuinely is KMS ECDSA P-256. The error was attributing that capability to us.) Scope widened 2026-10-03: this correction is not limited to the paper’s wording. Wherever this kit says receipt-backed or designed around verifiability — including the sample-copy card above, SOCIAL-COPY.md and BOILERPLATE.md — it means only that tests, deployment records and published limitations accompany a delivery for a reader to inspect. It does not mean our receipts can be cryptographically checked after the fact: per the HMAC layer described above, they cannot, by a third party or by us. This correction is about our own receipt layer; it does not speak to artefacts recorded or hosted elsewhere that we link to, which stand on their own public records. The paper is left downloadable and unedited so the record stays auditable; a corrected reissue is pending.