This page shows you how to resolve issues with Agent Registry.
API rate quota exceeded
You might encounter this issue if you interact with Agent Registry API or rapidly navigate through Agent Registry in Google Cloud console:
429 Too Many Requests
To resolve this issue, implement exponential backoff in your API clients to manage request rates. Agent Registry API has a default rate quota of 1,200 requests per minute globally and per region.
If you encounter throttling when switching tabs in Google Cloud console, wait a few
moments and try again. If your programmatic use case requires higher limits,
request a quota increase
for the RequestsPerMinute metric.
Payload size error during manual registration
You might encounter this issue if you manually register an agent or MCP server: the API rejects the request with an error stating that the payload is too large.
To resolve this issue, verify that your agent-card.json or toolspec.json
file is less than 10 KB. The AgentSpec and McpServerSpec content sizes are
limited to 10 KB. Minify your JSON files, remove unnecessary whitespace, or
condense tool descriptions to adhere to this limit. For more information, see
JSON schemas.
Missing agents or MCP servers after creation
You might encounter this issue if you create an agent or MCP server in a
supported Google Cloud product, such as Google Workspace or
Gemini Enterprise: the resource doesn't appear when calling the
ListAgents or ListMcpServers APIs.
To resolve this issue, wait for the background synchronization to complete. Your resources update in real-time, but other integrations are populated by offline batch jobs running periodically. If your resource doesn't appear after several hours, verify your project's Service Usage settings and ensure that the relevant API is enabled.
Long-running operations appear stuck
You might encounter this issue if you deploy agents or configure complex bindings: the operation takes a significant amount of time and appears stuck.
To resolve this issue, use the get_operation MCP tool or the
google.longrunning.Operations.GetOperation API endpoint to poll the
operation's status. Some agent and MCP backend creations require significant
infrastructure provisioning, which can lead to long-running operation (LRO)
times that might take up to 30 minutes. Configure your client timeout settings
as a result and poll the done boolean flag to verify completion.
Empty results when fetching available bindings
You might encounter this issue if you fetch available bindings for an auth
provider: the API returns an empty array or an access error, even if you
verified the binding exists.
To resolve this issue, verify that your principal has the correct
IAM permissions on the target AuthProvider resource. The API
applies strict IAM checks and removes Binding objects that
reference auth providers the caller doesn't have access to. Ensure that your
principal has the required access on the auth provider and the
roles/agentregistry.viewer role on the project.