Spec

Unofficial concept

Raw material

Before designing anything I used the live beta like a customer and like an engineer: every route at desktop and phone width, its network calls, four real jobs, the public explorer, and your Drive folder. This page is what came back.
See the redesign →
The beta's Terminal panel during the USPS job
The beta’s Terminal: the right data, in a debug panel.

Four real jobs

Captured 17 Oct 2026 00:43 UTC, in epoch 417 of 9-hour epochs: 1,918 registered providers across 71 ranked job types, 39,459 requests served, and one validator live on testnet.

QuestionRouted toAnswered byConfidenceProviderWhole jobCharged
Is this text message a scam? "USPS: Your package is on hold due to an unpaid customs fee of $1.99. Reply Y to reschedule delivery today."FRAUD_DETECTIONTelegraph Sentinel
#1 of 29, score 1.00
70%1.0 s32.4 s$0.01
Is this a scam? A text from an unknown number: "Hi mum, I dropped my phone in the toilet, this is my new number. Can you text me back here?"FRAUD_RISKRiskWire Fraud Risk
#1 of 11, score 0.69
92%4.8 s20.7 s$0.01
Is this name on the OFAC sanctions list: Viktor Bout?SANCTIONS_SCREENING_MATCHLiveCert — Sourced Answers for Agents
#1 of 14, score 0.68
95%3.5 s15.4 s$0.01
Is the online store bluecrestoutlet.shop legit or a scam?URL_SAFENo ranked providerNoneNone7.5 s$0.00
  • Is this text message a scam? "USPS: Your package is on hold due to an unpaid customs fee of $1.99. Reply Y to reschedule delivery today."

    Telegraph Sentinel · #1 of 29 · 70% sure · 32.4 s · $0.01

    FRAUD_DETECTION

  • Is this a scam? A text from an unknown number: "Hi mum, I dropped my phone in the toilet, this is my new number. Can you text me back here?"

    RiskWire Fraud Risk · #1 of 11 · 92% sure · 20.7 s · $0.01

    FRAUD_RISK

  • Is this name on the OFAC sanctions list: Viktor Bout?

    LiveCert · #1 of 14 · 95% sure · 15.4 s · $0.01

    SANCTIONS_SCREENING_MATCH

  • Is the online store bluecrestoutlet.shop legit or a scam?

    No ranked provider · 7.5 s · $0.00

    URL_SAFE

Each answer streamed as server-sent events: conversation, job, status (classifying), status (asking_miner, with the job type and provider), trace (the provider’s result and its x402 receipt), tokens, and done (answer, sources, timings). The redesign is built on exactly these fields.

Where the 34 seconds went on the USPS job

LLM calls took 20.1 s, other lookups 14.5 s, the provider itself under a second. Most of the wait is Anjoman, not the network, so the progress should show the network’s part honestly and move fast where Anjoman is slow.

  1. 23:28:14.862Request received — agentic routing enabled
  2. 23:28:17.498Working out what this question needs…
  3. 23:28:29.570Asking Telegraph Sentinel…
  4. 23:28:34.701Telegraph Sentinel (rank #1) · paid via x402 · payment verified $0.0100 · settlement on-chain (epoch 417)
  5. 23:28:35.308Provider result (992 ms)
  6. 23:28:49.440Job finished

Routes and states

Every route of the beta, signed out, on a 1536 px desktop window; the four main ones also on a 390 px phone.

RouteWhat’s thereSigned out
/Composer, then the job view in placeWorks signed out (free trial)
/docs/*About 20 pages: protocol, Intents, x402, WebSocket, MCPWorks
/dashboardOverview with Ask, Build and ExploreWorks signed out
/dashboard/activityMy ActivitySign-in wall
/dashboard/accountAccount & BillingSign-in wall
/dashboard/earn, /eval, /registrationsSupply toolsSign-in wall
/dashboard/validateValidator onboarding formWorks
/dashboard/buildAPI surfaces and example apps; key management “not built yet”Works
/dashboard/explore (+ miners, leaderboard, wasm, validators, signals)Public network explorerStats stay as skeletons; leaderboard never loads
/dashboard/explore/signals/:hashPublic signal recordWorks with the signal hash, “not found” with the receipt hash
/chatReferenced in the bundle404
  • /

    Composer, then the job view in place

    Works signed out (free trial)

  • /docs/*

    About 20 pages: protocol, Intents, x402, WebSocket, MCP

    Works

  • /dashboard

    Overview with Ask, Build and Explore

    Works signed out

  • /dashboard/activity

    My Activity

    Sign-in wall

  • /dashboard/account

    Account & Billing

    Sign-in wall

  • /dashboard/earn, /eval, /registrations

    Supply tools

    Sign-in wall

  • /dashboard/validate

    Validator onboarding form

    Works

  • /dashboard/build

    API surfaces and example apps; key management “not built yet”

    Works

  • /dashboard/explore (+ miners, leaderboard, wasm, validators, signals)

    Public network explorer

    Stats stay as skeletons; leaderboard never loads

  • /dashboard/explore/signals/:hash

    Public signal record

    Works with the signal hash, “not found” with the receipt hash

  • /chat

    Referenced in the bundle

    404

Stack, from the bundle: Next.js with Turbopack, Privy for sign-in and embedded wallets, x402 payments on Base Sepolia, and Fraunces with Inter Tight on a cream and rust palette. That palette is a close cousin of Claude’s, which is why the beta reads as a skin of it.

What I found

Ranked by how much each one costs a first-time user.

  1. 1. 34 seconds of one static line

    The provider answered in about a second, but the job took 34 s, and for the first ~15 s the only feedback is “Working out what this question needs…”. The redesign shows each real stage as it happens.

    The beta: 34 seconds of one static line
  2. 2. The proof is hidden

    Provider, rank and the provider’s own confidence sit behind a collapsed “Where this came from” toggle. The confidence (0.70 on my first job) never appears at all.

    The beta: the proof is hidden
  3. 3. “View signal” links to the wrong hash

    The Terminal links the receipt hash, which the explorer can’t find. The “How this was done” link uses the signal hash and works.

    The beta: “view signal” links to the wrong hash
  4. 4. The public record leads with raw JSON

    The signal page cuts the input mid-word (“…payload”:{“query”:“Is”), files user jobs under category “other” with interest 0.0, and shows the JSON before any human summary.

    The beta: the public record leads with raw json
  5. 5. An empty field sent to a provider

    On the “Hi mum” job RiskWire warned that the request’s question parameter arrived with length 0. It answered anyway, from the scenario text.

  6. 6. Explorer never finishes loading

    Network stats stay as skeletons and the leaderboard sits on “Loading leaderboard”. The integrations call it waits on returns 2.9 MB.

    The beta: explorer never finishes loading
  7. 7. Mobile header and Terminal

    At 390 px the header shows two identical dashboard icons, and opening a past job puts an empty Terminal over the conversation.

    The beta: mobile header and terminal
  8. 8. Shared links show no picture

    Anjoman pages declare a small 500 × 500 link card, and its image URL points at anjoman.telegraphprotocol.com, which didn’t load when I checked. Telegraph’s own site already uses the large 1200 × 630 card.

  9. 9. The wording outran the confidence

    On the USPS job the provider reported 0.70 confidence; Anjoman’s answer said “highly likely” and showed no number. Wording should follow confidence.

  10. 10. The router can be confidently wrong

    In the public feed, “Will JAB-23E73 complete Phase 1 trials?” went to credit-score verification at 0.9 confidence. The redesign shows the job type it picked and lets you change it.

The three references in the brief

Used hands-on, not from screenshots: what to take, and what to leave.

Claude

  • Take: One composer, generous space
  • Take: The answer first, detail in a side panel
  • Take: Copy and retry under every answer
  • Take: An honest working state
  • Leave: The cream and clay palette with a serif headline: the beta already copies it
  • Leave: A model picker

OpenRouter

  • Take: One balance for everything
  • Take: Usage by day
  • Take: An activity log: what, who served it, cost, latency
  • Take: Keys with their own spend limits
  • Take: Rankings from measured use
  • Leave: The model catalogue as the front door
  • Leave: Choosing providers yourself
  • Leave: Tokens as the unit: Anjoman prices per answer

OpenClaw

  • Take: What spread were screenshots of outcomes
  • Take: A mascot with lore
  • Take: A name people repeat
  • Leave: The chaos: a rename saga and scams within hours
  • Leave: With a token involved, the shared thing has to carry its own proof

Your brand material

Your Drive folder, at full resolution.

Nine Midjourney images, one recipe. Six of them are above. Every filename carries --profile ar5id1l --v 8.2 and a one- or two-word prompt: “anjoman”, “anjoman enlightened”, “anjoman oracle”, “anjoman guru cult leader”. The look lives in the profile code, not the words. With access to that profile, new images come out in your exact house style; without it, I matched the look with a grade measured on all nine.

Anjoman Logo.pdf, 14 pages. A red hood with a dark arched face in a gold sun ring, then purple, black and navy variants, then dozens of turbans, seers and crystal balls. Many directions, no decision. One note on page 6 is the best idea in it: the face fills with light when your outcome is ready. The mark is built on that.

Telegraph. Hermes, the engraved winged messenger with cables; the Σ mark; the graded-diamond metaphor; MACHINA.