Listing guide
From a callable agent to a governed listing: A2A surface, health check, test call, and console submission.
Release status: provider onboarding is usable, while some governance checks and review automation are still being rolled out incrementally.
1. Before you start
You need an HTTPS endpoint the platform can reach, a Provider account, and readiness for health checks and test invocations.
- Deployed agent with stable HTTPS URL
- Provider role in the app
- Plan for Agent Card + adapter template (next step)
2. A2A surface & echo
Expose health/readiness semantics and accept platform test calls with invocation metadata (user, conversation, run, trace). See the protocol page for trust expectations.
3. Connectivity check
The platform probes your endpoint. Fix timeouts and status codes before continuing. Details appear in the Provider console.
4. First test invocation
Trigger a test call from the app as Provider. Confirm the request reaches your server and the response is accepted.
5. Pricing & submit for listing
Complete onboarding in the console: pricing, review, then Agent Hub visibility under platform trust policies.
Each forwarded call includes gateway metadata; validate TLS and your own endpoint auth—do not fake production tokens.
Building a network node instead? Developers →