Google Service Directory API

Can I use Service Directory for on-prem services?

Yes. Endpoints record arbitrary address and port values, so you can register on-prem or third-cloud services and resolve them from clients running in GCP or via Cloud DNS forwarding zones.

What are the rate limits for the Service Directory API?

Google enforces a default per-project quota of 600 read requests per minute and 60 write requests per minute on the registry resources. Resolve calls have higher per-region limits because they sit on the discovery hot path.

How do I resolve a service through Jentic?

Run the Jentic search query 'resolve service directory endpoints', load POST /v1/{+name}:resolve, and execute it with the service resource name. Jentic injects the GCP credentials so the agent only needs the service name and an optional max-endpoints filter.

Does Service Directory health-check endpoints?

No. Service Directory stores the endpoints you register; health checking is the responsibility of the registering workload or a fronting load balancer. Clients should still validate health on their side after resolving.

Can I expose Service Directory entries through DNS?

Yes. Cloud DNS supports a Service Directory zone type that mirrors a namespace as a private DNS zone. Updates to endpoints propagate to the DNS view automatically without separate record management.

Can I limit what my agent is allowed to do with the Service Directory API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Service Directory operations and credentials your agent may use. Since the namespace and service sit in the URL path (like /v1/{parent}/services and /v1/{name}:resolve), you can pin the agent to a single namespace so it registers services and resolves endpoints there and nothing else. You pick the exact operations it may call, so an action like deleting a service is excluded unless you add it, and the OAuth credential stays with your own instance rather than the agent's context.