x402 inspect: fallback to on-chain gateway balance when API balance is stale#49
Merged
Abiorh001 merged 1 commit intoApr 22, 2026
Conversation
Abiorh001
approved these changes
Apr 22, 2026
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
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
Why
In real runs, Gateway API /v1/balances can lag after deposit while on-chain �vailableBalance is already funded. This causes false �uyer_ready=false in /api/v1/x402/inspect.
Changes
src/omniclaw/agent/routes.py
ests/test_x402_sdk_adapter.py
update existing route-selection tests to mock get_gateway_onchain_balance
add est_choose_x402_route_uses_onchain_fallback_when_api_balance_is_stale
Verification