A bounded first review
Bring up to ten public dependencies from one project. We agree the scope, inspect the recorded evidence together and identify which changes deserve attention. Admission and scheduling are confirmed individually.
AGENSTRY / AGENCY PILOT
Give your clients a record
of what their agents depend on.
For agencies and small teams maintaining external A2A agents and MCP integrations. Start with a few public dependencies and review whether the evidence helps your actual work.
Useful client artifacts
Use public evidence report links, a locally downloaded setup report and the CI guide to document the review. Keep private client names, credentials and configurations in your own systems.
An explicit next decision
Agree which dependencies to watch, who reviews a change and whether the current Free or paid plan fits. A pilot application creates no subscription or contract. Any additional work and price are agreed before it starts.
What to include in your application
- Your team's role and the integration problem you are trying to solve.
- The approximate number of public dependencies and clients involved.
- Whether the need is migration help, change monitoring or CI review.
Do not send secrets or client configurations. You can describe private dependencies without naming their hosts; public runtime evidence may not cover them.
We measure public observations. The pilot does not promise security certification, guaranteed uptime, a score increase, customer referrals or a replacement for provider authentication.
Open the pilot applicationAlready building a client or directory?
Our public evidence API and free comparison can support your own user interface. Use the API's normal rate limits, preserve observation dates and unknown states, and link each observation to its Agenstry record. Talk to us before a larger integration.