Repository navigation
Complete the first agent call from the browser dashboard - #59
Merged
Merged
Conversation
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.
The developer dashboard previously stopped at a copyable code sample after key creation. A newly created key can now send an A2A message through the existing production gateway without leaving the browser. The form lists approved, healthy, free hosted agents, keeps the one-time key in page state, and sends the credential only to the same-origin gateway. The gateway declines a call if the selected agent has become paid.
The message endpoint finishes metering before returning. The usage chart and recent-call table also count JSON-RPC failures returned over HTTP 200. Two route tests exercise the pricing guard and immediate usage visibility. All dashboard locales include the new controls.