ops+fix: upgrade to v2.0.0 — x402 compliance, 74 endpoints, Node 24, FRED env#13
Open
KelleyHuntPLLC wants to merge 2 commits into
Open
ops+fix: upgrade to v2.0.0 — x402 compliance, 74 endpoints, Node 24, FRED env#13KelleyHuntPLLC wants to merge 2 commits into
KelleyHuntPLLC wants to merge 2 commits into
Conversation
added 2 commits
June 5, 2026 08:10
…PI_KEY to render.yaml - Update x402.json, llms.txt descriptions: 66+ → 74+ paid endpoints, 18+ → 22+ sources - deploy-verify.yml: add RENDER_API_KEY path, extend wait to 8 min, Node 24 env - All workflows: FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true (deprecation fix before Jun 16) - render.yaml: add FRED_API_KEY and HYDRA_RELAYER_URL placeholder env vars This push triggers Render autoDeploy to land v2.0.0 on the live service. Master has been at v2.0.0 since c800806 but Render's autoDeploy queue was blocked. Co-authored-by: HYDRA Agent <hydra-agent@perplexity.ai>
The 402 response body now follows the x402 v2 spec:
{ "x402Version": 2, "error": "Payment Required", "accepts": [{...}] }
Previously the body used a custom format with payment details in nested
objects, which caused x402scan.com, x402 Bazaar, and all spec-compliant
x402 client libraries to fail to discover/parse payment requirements.
Changes:
- 402 body root: x402Version=2, error=..., accepts=[{scheme, network, ...}]
- accepts[0] contains all required spec fields: scheme, network,
maxAmountRequired, resource, description, mimeType, payTo,
maxTimeoutSeconds, asset, extra
- protocol_version bumped to 2 in payment_methods.x402
- HYDRA extended fields preserved for backward compatibility
- PAYMENT-REQUIRED header (base64 encoded) retained
Impact: HYDRA is now discoverable by x402scan.com, x402 Bazaar,
and any x402-spec-compliant agent. All 74 paid endpoints will
appear in x402 directory crawls after next deploy.
Co-authored-by: HYDRA Agent <hydra-agent@perplexity.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two commits that upgrade HYDRA to v2.0.0 and fix x402 protocol compliance.
Commit 1:
927c1af— ops: fix manifests, upgrade CI to Node 24, add FRED_API_KEYFRED_API_KEYandHYDRA_RELAYER_URLplaceholder env vars to render.yamlCommit 2:
5ffc63b— CRITICAL: x402 protocol compliance fixx402Version: 2,error, andaccepts[]array at rootAfter merge
Wallet:
0x2F12A73e1e08F3BCE12212005cCaBE2ACEf87141(Base mainnet, USDC)