Skip to content

docs(readme): surface the Bazantic gateway a judge can call - #30

Closed
edycutjong wants to merge 1 commit into
mainfrom
feat/bazantic-badge
Closed

edycutjong wants to merge 1 commit into
mainfrom
feat/bazantic-badge

Conversation

@edycutjong

Copy link
Copy Markdown
Owner

Bazantic is the second partner prize, and the gateway it produced was reachable only from the runbook — a judge reading the README had no way to see the API is registered and serving through it.

The badge targets /api/retainer/status rather than the gateway root: the root is not a page and answers 404 the same way HashScan does, while the status endpoint returns 200 with real chain-backed JSON. Verified before committing:

URL
retainer-x402.bazgateway.com (root) 404
…/api/retainer/status?agent=0xD14C… 200
…/mcp 405 (POST-only, expected)

Shortest path from "they claim a gateway" to "the gateway answered me".

Bazantic is the second partner prize, and the gateway it produced was reachable
only from the runbook -- a judge reading the README had no way to see that the
API is registered and serving through it.

The badge points at the status endpoint rather than the gateway root, because
the root is not a page: it answers 404 the same way HashScan does, while
/api/retainer/status returns 200 with real chain-backed JSON. It is the shortest
path from "they claim a gateway" to "the gateway answered me".
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
build Building Building Preview Sep 9, 2026 2:59pm UTC

@edycutjong

Copy link
Copy Markdown
Owner Author

Closing — the information is already on all three surfaces, and Bazantic's own qualification requirements don't ask for README placement.

Already present:

  • README.md:212 (agent-interface table), :454 and :460 (a full section on the gateway + marketplace)
  • app/page.tsx:415, :435 (landing page body)
  • pitch-deck.html (2 mentions)

Bazantic's Best Recipe requirements are: bazantic.com account, x402/MPP gateway, a second service (Hedera Mirror Node), a recipe joining them — all done — plus a screen recording of the flow end to end and the bazantic username in the submission, neither of which a README badge satisfies.

The CTA row is the first thing Hedera and finalist-round judges read; a seventh badge pointing at raw JSON dilutes it without earning anything on the Bazantic side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant