chore(vibenet): migrate API calls to api.vibes.base.org - #13
Merged
Conversation
The vibenet dataplane API is moving off the apex host onto a dedicated hostname. Point every apex API reference at api.vibes.base.org so nothing here breaks when vibes.base.org later becomes a redirect: - client.ts DEFAULT_BASE_URL and .env.example NEXT_PUBLIC_VIBENET_API_BASE_URL -> https://api.vibes.base.org (this also repoints the account rpc/payer/ bundler URLs, which derive from it) - SKILL.md + chains.ts doc references to /api/vibenet/* on the apex RPC (rpc.vibes.base.org) is a separate host and is intentionally unchanged. Verified api.vibes.base.org returns identical 200s (health/config/contracts/ explorer/faucet). typecheck/lint/build/tests pass.
Collaborator
🟡 Heimdall Review Status
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
What
Point every vibenet dataplane API reference at the dedicated hostname
api.vibes.base.org, off the apexvibes.base.org.Why
The vibenet APIs are moving off the apex onto
api.vibes.base.org. Both hosts currently return identical responses, so this is non-breaking and ships independently. Once apex traffic drains,vibes.base.orgbecomes a redirect to a landing page — at which point any remaining apex API calls would break. This makes sure nothing here calls the apex.Changes
app/vibenet/library/client.ts—DEFAULT_BASE_URL→https://api.vibes.base.org. Also repoints the account demo'srpc/payer/bundlerURLs, which derive from it..env.example—NEXT_PUBLIC_VIBENET_API_BASE_URLdefault.chains.ts+build-with-viem-eip8130.SKILL.md— doc references to/api/vibenet/*on the apex.Intentionally unchanged
All
rpc.vibes.base.orgreferences (config.ts,build/page.tsx, SKILL.md) — RPC is a separate host.Verification
api.vibes.base.orgreturns identical HTTP 200s before/after (health, config, contracts, explorer stats/blocks, chain-health, faucet status).typecheck,lint,tests(10/10),buildall pass.grep -rn "vibes.base.org"leaves only the intentionalrpc.host + the migratedapi.base.