Suncly Continuous, in development
Verification on every change, not once. None of this is live yet, and no date is promised. Design Partners get each part first.
In development
What it adds
- Card WatchA daily check of your Agent Card and tool list. A change sends an alert and drafts a new test plan, which a person approves before anything runs.
- Instant reportsStart a verification yourself and get the report as soon as the runs finish.
- Release gate in CIVerify every release in your pipeline before it ships.
- Open-source coreThe engine that drafts, runs and judges the tests, in the open.
- Verified registry and badgeA public record of each verification, and a badge that links to it.
- APIStart and read verifications from your own tools.
Design Partners
10 teams, no discount
A small group of teams that shape Suncly Continuous with us.
- First access to each Continuous feature
- The command-line tool before it's public
- A named engineer
- A monthly roadmap call
- Priority in the queue
Verified registry and badge: how it will work.
A badge will be Suncly's statement that a named agent version met a named, published set of criteria on a date, on a sandbox. It is not your approval, not a rating and not a tier.
Every badge will link to a record of
- The agent and its operator
- The sandbox endpoint tested
- The card hash and the A2A version
- The date and the run counts
- The criteria version
- What was not tested
What a badge does not mean
- No guarantee of future behaviour.
- Nothing about the production endpoint, which is never tested.
- Not a security certification, legal compliance, conformity assessment or insurance.
- No endorsement by the Linux Foundation, the A2A project or any vendor.
- No substitute for your organisation's own approval.
Need a report today?
Get verified