Product and demos
Describe the consequential action, not a generic use case
The fastest way to evaluate Agnys is to identify an agent action your team would need to reconstruct after the fact. That might be a file modification, shell command, external API call, sensitive-data access, approval decision or production change. Include the agent or framework you use, the systems it can touch and the reviewers who need the resulting evidence.
A product conversation can then focus on capture boundaries, integration options, latency and reliability considerations, retention, access and export requirements. A demonstration is most useful when it follows a representative run from trigger through side effect instead of touring every screen. Use the demo form or email contact@agnys.net with enough non-sensitive context to prepare the discussion.
- Agent, framework or developer environment in scope
- Tools, files, commands or business systems the agent can affect
- Security, engineering, audit or customer-assurance questions the record must answer
Benchmark and research
Challenge the Agent Evidence Benchmark
Agnys is developing the Agent Evidence Benchmark as a public, scenario-based way to compare the quality of operational records produced by agent evidence systems. Practitioners in observability, security, agent engineering, audit and governance can review the dimensions, scenarios and scoring language before product results are published.
Feedback is especially useful when it identifies an evidence relationship that the current method misses, a scenario that cannot be repeated safely, or wording that would let a vendor receive credit without producing reviewable support. Send comments to contact@agnys.net with the subject Agent Evidence Benchmark review. Disagreement is welcome when it improves the method.
Corrections
Report an inaccurate or outdated claim
Technical standards, product support and regulatory timelines change. If a page on agnys.net appears inaccurate, send the page address, the statement at issue and a primary source or reproducible observation when available. Agnys can then investigate the specific claim rather than guessing which passage needs attention.
A correction request does not need to be formal. Clear evidence is more useful than polished language. Product security issues should not include secrets, credentials, live personal data or exploit details in an ordinary website form. Begin with a concise description and request a suitable channel for sensitive material.
Privacy questions
Ask how website inquiry information is handled
The demo form requests a name, business email, company, company size, primary use case and message. It also records a submission timestamp and sends the inquiry through the form service used by the site so Agnys can respond and arrange a product conversation. Do not place passwords, API keys, production data, real personal records or other secrets in the message field.
Questions about this website's privacy notice, access to inquiry information or a request to correct or delete submitted information can be sent to contact@agnys.net. Requests may require reasonable verification so information is not disclosed or changed for the wrong person. The website privacy notice explains the scope and limits in more detail.