[eddiemessiah]

The hole, and the fix

The Agents section documents ERC-8004, x402, MPP, fee abstraction and stablecoin payments one primitive at a time, but has no page showing an agent app on Celo that combines them. AskBots is one, and the docs did not mention it anywhere (git grep -i askbot on main returned nothing).

This PR adds build/agents/askbots.mdx, a Guide-type page that presents AskBots as an example of the agent economy on Celo:

• How it works: a sequence diagram plus the same six steps in text (builder creates and funds a project, agents answer, quality checks, payout, results and round two).
• Celo features it uses: a table mapping USDT payments, the on-chain escrow, ERC-2612 permit funding, fee abstraction and ERC-8004 identity to what AskBots does with each, linking the relevant docs pages.
• Ask for feedback (builder path, dashboard or CLI) and Onboard an agent (agent path, via the skill file).
• Troubleshooting with the exact HTTP status codes and CLI exit behaviour, then Resources and Related.

It also lists the page in the Agents group of docs.json (after MPP), adds a short "Getting feedback from agents" section to the Agents overview (AGENTS.md §8.9), and adds a Related bullet on the ERC-8004 and x402 discovery pages.

What this does NOT do / residual risk

• No contract addresses are listed (AGENTS.md §7). The page names the escrow and links the ERC-8004 registries to /build/agents/8004.
• The page does not claim that AskBots writes reputation feedback to the ERC-8004 Reputation Registry. It only states that every reviewing agent registers an ERC-8004 identity, which the agent registration flow requires.
• No screenshots of the signed-in dashboard; the page uses a mermaid diagram and text only, so nothing on it shows user data.
• The CLI example was checked against the CLI's README and command list, but was not run end to end here, because step 4 funds a real project on Celo mainnet.

Judgement calls

• Disclosure: I contribute to AskBots.
• Operator: the page does not say who operates AskBots, and links no source repository. @GigaHierz, how would you like the operator described?
• Amounts in USDT, not dollars: Mintlify renders text between two $ signs as math, which turned "$0.11: $0.10" into a formula in the preview. Amounts are written as "0.11 USDT", which is also the token actually paid.
• Sidebar title "AskBots (agent feedback)", following the descriptive pattern of "Celina (agent wallet)".
• Not linked from usecases.mdx: that page has no Related section, and adding one would widen this PR.

Issues

Refs: none.

Stacking / conflicts

Based on current main (de25c440). The only other open PR touching docs.json is #2372 (Pinax), which edits the indexers group, not Agents.

Verification evidence

Facts, checked on 2026-10-08 and re-checked 2026-10-12:

Claim on the page	Source
0.11 USDT per response: 0.10 to the agent, 0.01 platform fee	Escrow costPerResponse() = 100000 and platformFeePerResponse() = 10000 (6 decimals) via forno eth_call; askbots.ai/api/chain returns the same
Funding token is USDT on Celo mainnet	Escrow usdt() returns 0x48065fbBE25f71C9282ddf5e1cD6D6A887483D5e, whose symbol() is "USD₮"
Gasless web funding via ERC-2612 permit	Escrow createProjectWithPermit, commented "using an ERC-2612 permit signature"
Five property types, 1-20 questions, four question types	AskBots skill file and CLI README
40 accepted reviews per agent per UTC day; one review per project; 422/409/429	AskBots skill file; daily cap constant in the AskBots source
Agents register an ERC-8004 identity from the payout wallet	AskBots skill file; askbots agent register-identity
CLI package and version	npm view askbots version -> 0.5.0
CLI never takes a key as a flag	AskBots CLI README: "read from the environment only, never from a flag"

Outbound links, curl -sL on 2026-10-12: askbots.ai, /docs, /skill.md, /leaderboard, /dashboard/new all return 200. npmjs.com/package/askbots returns 403 to curl (npm blocks non-browser clients) and loads in a browser.

Local preview (mint dev), Playwright, dark theme:

• Desktop 1280px: scrollWidth 1280, no page-level overflow.
• Phone 412px: scrollWidth 412; code blocks and the diagram scroll inside their own containers, as on other pages.
• 0 console errors at both widths.
• The diagram renders; the page appears in the Agents sidebar; the overview, ERC-8004 and x402 discovery pages each link to it.

mint broken-links reports false positives on this Windows machine, so I am relying on the repository's "Check for broken links" run for this head.

Remaining ops steps

None.

Checklist

• Title is the commit message I want on main
• Ships the test that fails on pre-fix code (n/a: docs content)
• Covers the seam (n/a)
• Error responses audited (n/a)
• Judgement calls flagged above
• Local preview on the current head, desktop and phone, 0 console errors
• Re-read acceptance criteria of every Closes issue (no Closes)
• Development sidebar links match Closes/Refs above
• README / runbook / examples updated (n/a)
• Lockfile touched (n/a)
• Wallet/provider tree touched (n/a)
• UI touched: browser pass at desktop and phone
• Money/security path (n/a)
• No secrets in the diff
• Questions for the maintainer: the operator wording above

🤖 Generated with Claude Code

[GigaHierz]

Reviewed the final diff: builder credit is consistent across the page, overview and Use Cases, internal links resolve, and the product figures were checked against the AskBots source.