Add Agent Gateway to Gateways (hosted)#66
Closed
Robocular wants to merge 1 commit intoKikobeats:mainfrom
Closed
Conversation
Author
|
Closing in favor of #68 which has improved formatting. |
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.
Proposed addition
Adds a Hosted subsection under
## Gatewayswith one entry: Agent Gateway.What is Agent Gateway?
Agent Gateway is a hosted API gateway that unifies 39 microservices under a single API key:
Free tier: 50 calls/day without signup. Pay-per-use credits beyond that.
Why a new subsection?
The existing
### Open Source / Self-hostedentries are infrastructure gateways you deploy yourself. Agent Gateway is a complementary pattern — a hosted/managed multi-service gateway — which warrants its own subsection to keep the distinction clear for readers.