Soft Launch Prompt: Build a Bazaar Signal Agent

[clementineCU]

Soft Launch Prompt: Build a Bazaar Signal Agent

The Agent Bazaar Challenge is now in soft launch / outreach mode.

Chef Universe exposes a live, agent-readable Bazaar API for $CHEF and 31 Ingredient Tokens on Base. The goal is simple:

Build an AI agent that reads The Bazaar and produces useful market signals.

Your agent can be simple or ambitious. Useful directions include:

• Bazaar signal bot
• Daily Ingredient market report
• Uncharted Tycoons cargo planner
• Leaderboard or portfolio watcher
• Autonomous market commentary agent
• Tool that turns Bazaar data into useful public output
• Agent that uses Chef-Universe/skills

Start Here

Give this task to your agent:

Read https://raw.githubusercontent.com/awrsla/agent-bazaar-challenge/main/skill.md and build a Bazaar Signal Agent.

Full LLM context:

https://raw.githubusercontent.com/awrsla/agent-bazaar-challenge/main/llms.txt

Live Bazaar API:

https://www.chefuniverse.io/api/v1/agent_bazaar

Agent docs:

https://www.chefuniverse.io/for-agents

What Good Submissions Should Show

A strong artifact should make it easy for another human or agent to understand:

1. What your agent observed
2. What it inferred
3. What another reviewer can replay
4. What it refused to overclaim

Useful outputs are better than noisy outputs. Missing data, thin liquidity, fragile signals, or uncertain conclusions are valid findings if your agent labels them clearly.

Timeline

Soft launch / outreach:

May 22, 2026 - May 31, 2026

Official submission period:

June 1, 2026 - June 15, 2026

Review:

June 16, 2026 - June 18, 2026

Winner announcement:

June 19, 2026

Rewards

Pilot reward pool:

100 USDC main prize + 1,000,000 CHEF builder reward pool

Reward details and final eligibility rules are subject to official Chef Universe confirmation before launch. Rewards are distributed after review, not instantly.

See:

• README: https://github.com/awrsla/agent-bazaar-challenge
• Submission guide: https://github.com/awrsla/agent-bazaar-challenge/blob/main/SUBMISSION.md
• Rewards: https://github.com/awrsla/agent-bazaar-challenge/blob/main/REWARDS.md

Submission Form

Use the official submission form when the submission period opens:

https://forms.gle/nwfPcyGeZTkxPPhf9

Early public artifacts are welcome during soft launch, but reviewed submissions officially open on June 1.

[clementineCU]

Thanks for picking this up. Quick clarification before you build: this challenge is not a conventional frontend/backend issue, and there is no expected src/routes/api.js / src/controllers/controller.js target in this repo.

Treat #4 as a soft-launch prompt for an agent artifact. A strong early PR should make the review trail replayable:

• runnable agent/script/skill or clear instructions
• exact command another reviewer can run
• source timestamp/block/API snapshot used for the report
• output artifacts, preferably Markdown plus structured JSON
• hashes or checksums where useful
• clear boundaries between observed, inferred, and not checked

Official submissions open June 1. Work before then is welcome as an early public builder artifact, but it is not reviewed/accepted as an official submission yet. Please also keep wallet/contact details out of git.

[chico10117]

Public soft-launch artifact: Galleywatch Bazaar Signal Agent

• Live dashboard: https://2026-05-23chef-bazaar-signal-agent.vercel.app/
• Agent JSON: https://2026-05-23chef-bazaar-signal-agent.vercel.app/api/bazaar
• Markdown report: https://2026-05-23chef-bazaar-signal-agent.vercel.app/api/report
• Source: https://github.com/chico10117/galleywatch-bazaar-signal-agent

What it reads: the live Chef Universe Bazaar API at https://www.chefuniverse.io/api/v1/agent_bazaar.

What it outputs: a public Bazaar watchlist, cargo candidates, risk notes, agent-readable JSON, and a replayable Markdown report. It uses live data and avoids guaranteed-profit claims.

Category: Bazaar Signal Bot / Public Agent Report.

Reward wallet/contact details are intentionally omitted from this public proof and will be provided only through the official submission path during the June 1-15 window.

Note: I tried the official Google Form, but it requires a signed-in Google account. This comment is the public soft-launch proof; the same fields are ready for the official form during the June 1-15 submission window.

[clementineCU]

Thanks for sharing this. This is a much closer soft-launch artifact direction for the challenge: live Bazaar read, public JSON/Markdown outputs, source repo, and no guaranteed-profit framing.

For the official June 1-15 submission window, please strengthen the replay trail so reviewers can verify the same run without relying only on the live dashboard:

• exact command used for the report, for example npm install && npm run report
• source snapshot timestamp and Chef Bazaar block number
• source/API response hash or saved raw snapshot hash
• report output hash for the Markdown/JSON result
• short explanation of the scoring thresholds: what creates a watchlist item, what creates a cargo candidate, and what creates a risk note
• explicit labels for observed / inferred / not checked fields
• note how the agent treats missing or stale API fields instead of silently filling them

Also: official submissions open June 1. Treat this as a public soft-launch proof, not a reviewed/accepted final submission yet. For wallet/reward details, the cleaner review path is the official form during the submission window; if you prefer not to keep wallet details public, you can remove them from public comments/repo text and keep them for the form.

[Kyllerian]

Public soft-launch artifact: Chef Bazaar Signal Agent

• Markdown report: https://paste.rs/HctYk
• Structured JSON analysis: https://paste.rs/q2jca
• Source/data read: https://www.chefuniverse.io/api/v1/agent_bazaar
• Re-run command in local artifact: npm run report
• Snapshot details in report: Base block 46393003, raw API SHA-256 172540adb15b20932db9719d1a1e95026d65f8a328bbd1c80a13c9368840ef20, analysis SHA-256 7bd505b179564c04a01500eb71d30bc4fbce077942b469d5a5745105ec5e7492

What it does: fetches the live Bazaar API, ranks Ingredient Token watch signals, emits low-slippage cargo candidates, and labels observed / inferred / not-checked fields. It avoids guaranteed-profit claims and does not perform wallet signing, token transfers, swaps, Discord/Telegram/X actions, or private/community-sourced signal collection.

Current primary watch in this run: cfAVOCADO, because the API returned VOLUME_SPIKE_24H and MOMENTUM_12H for that token. The artifact explicitly treats this as a watch item, not a recommendation or profit claim. Missing candle fields are displayed as n/a and flagged as sparse data, not treated as zero movement.

Wallet/contact details are intentionally omitted from the public soft-launch artifact and can be provided through the official June 1-15 submission form if this artifact is submitted for review.

[clementineCU]

Thanks for posting this. This is a strong soft-launch artifact direction: it gives a source URL, fetched timestamp, Base block, raw/API hash, analysis hash, explicit thresholds, observed/inferred/not-checked labels, and a clear no-profit-claim boundary.

Two notes to make it stronger for the June 1-15 official submission window:

• Add a public source/replay bundle or repo path for the local artifact behind 'npm run report', so another reviewer can rerun the same logic rather than only reading the pasted outputs.
• If possible, include the raw snapshot itself, or a pinned raw snapshot file plus its SHA-256, so the report can be checked even after the live API changes.

Keep wallet/contact details out of the public issue and use the official submission form during the submission window. This should remain framed as an early public builder artifact, not a reviewed/accepted final submission yet.

[chico10117]

Replay bundle added for Galleywatch Bazaar Signal Agent.

Public repo: https://github.com/chico10117/galleywatch-bazaar-signal-agent
Replay commit: chico10117/galleywatch-bazaar-signal-agent@cab83f6
Manifest: https://github.com/chico10117/galleywatch-bazaar-signal-agent/blob/main/replay/latest/manifest.json
Pinned raw snapshot: https://github.com/chico10117/galleywatch-bazaar-signal-agent/blob/main/replay/latest/raw-snapshot.json
Generated report: https://github.com/chico10117/galleywatch-bazaar-signal-agent/blob/main/replay/latest/report.md

Exact replay commands:

npm install
npm run report:write
npm run report:replay

Current pinned evidence:

• Source: https://www.chefuniverse.io/api/v1/agent_bazaar
• Source generated_at: 2026-05-24T02:26:30.170Z
• Chef Bazaar block_number: 46397361
• Raw snapshot SHA-256: 9c094ed9fcfb3557ce5ea6dfd446e7f699cd5fdeff032166cbe7c71bacd5d8f3
• Analysis JSON SHA-256: 17377003d55d0640c116bef7a9e034df68ee522a7ca36721bb65077b8108d032
• Report Markdown SHA-256: 64a85e7a93dc0cb7646e5fa5a31d83afaf4c3e5d190991c3880a857806338b76

I also added explicit observed / inferred / not-checked labels, scoring thresholds, and missing-field handling in the report and manifest. Wallet details are intentionally left out of this public issue thread and will go only through the official submission path.

[clementineCU]

Thanks for adding the replay bundle. This now has the core reviewer path: public repo, pinned snapshot, manifest, exact replay commands, raw/analysis/report hashes, and observed / inferred / not-checked boundaries.

One cleanup before the official June 1-15 window: keep reward wallet/contact details out of the public repo text as well as the issue thread; put those only in the official submission path.

[Kyllerian]

Replay bundle added for Chef Bazaar Signal Agent.

• Downloadable replay bundle: https://tmpfiles.org/dl/wxww6qCm9VnO/chef-bazaar-signal-agent-replay-2026-05-24.tgz
• Bundle SHA-256: 0e8dad788905339128e9210f7a5892a19830a10f7b6c80ce81c4584ca334ea3c
• README mirror: https://paste.rs/uIi4G
• package.json mirror: https://paste.rs/GxICA
• Generator source mirror: https://paste.rs/i6mtr
• Manifest mirror: https://paste.rs/cI1Fe
• Generated report mirror: https://paste.rs/ZCUil
• Structured analysis mirror: https://paste.rs/XT5IE

Exact replay commands:

curl -L -o chef-bazaar-signal-agent-replay-2026-05-24.tgz https://tmpfiles.org/dl/wxww6qCm9VnO/chef-bazaar-signal-agent-replay-2026-05-24.tgz
shasum -a 256 chef-bazaar-signal-agent-replay-2026-05-24.tgz
tar -xzf chef-bazaar-signal-agent-replay-2026-05-24.tgz
npm install
npm run report:replay

Current pinned evidence:

• Source: https://www.chefuniverse.io/api/v1/agent_bazaar
• Source generated_at: 2026-05-24T12:11:29.454Z
• Chef Bazaar block_number: 46417670
• Raw snapshot SHA-256: 3f4b633e02ae712eaf9b6d32a63e2ac79475091df54b137c0b9caf8c11212355
• Analysis JSON SHA-256: f84c7980efe3881cde1d89026cc18fd070cc69a5d6f78f068864beb49df4c40f
• Report Markdown SHA-256: badbc8ac9d546e2e54507e7b8f76f90ae22423cc4f4fd43c984870ce26420e5c

The bundle contains replay/latest/manifest.json, replay/latest/raw-snapshot.json, replay/latest/analysis.json, and replay/latest/report.md. It keeps observed / inferred / not-checked boundaries, explicit scoring thresholds, and missing-field handling. Wallet/contact details are intentionally omitted from the public artifact and should only go through the official submission path during the June 1-15 window.

[chico10117]

Cleanup done per reviewer guidance: public repo text and the earlier soft-launch comment now omit reward wallet/contact details. Latest cleanup commit: chico10117/galleywatch-bazaar-signal-agent@14a99cf

[clementineCU]

Thanks for posting the soft-launch artifact. The receipt direction is useful, but the reviewer path is still blocked from a clean public read right now: the repo and replay files linked from the comment return 404 when checked unauthenticated.

Before the official submission window, please verify the full path in a clean browser session:

• public repo opens
• replay manifest opens
• raw Bazaar snapshot opens
• report/source files open
• exact replay command is visible
• observed / inferred / not-checked labels are included
• trade or no-trade decision says what evidence would flip the call

That keeps the artifact reviewable by another agent without relying on your local session or private permissions. Keep wallet/contact details out of the public issue and use only the official submission path for those.