frontend/src/lib/config.ts told operators to set VITE_API_BASE to
cred402.onrender.com (no -1) — a stale duplicate Render deploy still
running an old pre-Algorand build. Every other reference in the repo
(render.yaml, README, vercel.json rewrites, docs, examples) already
points at the canonical cred402-1.onrender.com. Fixed the comment and
documented the duplicate-service cleanup (owner-gated, no Render API
token available here) in docs/ACTIVATION_CHECKLIST.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The GoPlausible facilitator writes Global x402 Challenge attribution at
settlement time from accepts[].extra.tag, and never backfills it. It does
not persist the x402 resource.tags array into its Bazaar record: of 200
live Bazaar resources, 176 carry the tag via extra.tag and zero have a
tags field at all.
Cred402 advertised the tag only in resource.tags, so a real Mainnet
payment would have settled, catalogued into the Bazaar, and then been
filed under src=direct -- never reaching the challenge leaderboard.
- move the tag into the accepted option's extra, from a shared
challenge_tag module so server and client cannot drift
- declare the x402-merchant extension so the leaderboard row carries a
name and logo instead of a bare hostname
- reject a challenge missing extra.tag in inspectAlgorandChallenge, which
fails both the preflight and the release gate
- assert it in the gateway test and in both buyer examples
- add x402:algorand:challenge-check, a read-only gate over the status
probe, the Bazaar catalogue and the challenge leaderboard
Attribution is not retroactive, so this has to ship before the first real
payment.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The pricing and docs pages headlined a live, buyable 0.01 USDC endpoint while
the deploy returns 503 (configured:false) — selling a dead product.
- pricing.html: badge/CTA/spec now read GET /v1/x402/algorand/status and render
'activating', live-testnet, or live-mainnet states; example labeled illustrative;
JSON-LD availability -> PreOrder until the probe confirms live
- api-docs.html: live-status banner up top so a developer sees on/off before coding
- both degrade gracefully on cold-start/probe failure (never claim live)
- docs/ACTIVATION_CHECKLIST.md: exact owner env checklist to flip the probe to
configured:true (pay-to, network, facilitator, indexer) + durable CRED402_DATA_DIR
persistence + mainnet gates