AgentLens

ZhangJinHaHaHa/AgentLens is ranked 12,046 among these 8 peers; tensorlakeai/tensorlake is ranked 12,027.

Users can discover task-specific Agents, compare evidence and execution boundaries, rent a supported Agent, and run it with platform-provided model, search, file, artifact and audit capabilities. The platform follows a simple boundary: **AgentLens provides the brain and governed runtime; sellers provide the specialized Agent. ** Renting an Agent grants time-limited execution access. It does not transfer source code or permanent ownership. This repository is the sanitized public source distribution. It contains the public product surface, contracts, integration schemas

and non-sensitive audit reference code. Hosted Brain strategies, production routing, Workers, capability-broker policy, quality scoring, billing ledgers, credentials, topology and deployment automation remain private. What Is Public **Marketplace and decision UI**: browse, compare, inspect trust evidence and understand how an Agent can be used. **Rental-only smart contracts**: time-limited access, reviews, audit records, appeals and reputation primitives. **Audit reference implementation**: six-dimensional evaluation, evidence persistence, attestation adapters and ZK verification components. **Agent Contract v3 and Wire v1

**: tasks, streaming events, tools, checkpoints, cancellation, resume, artifacts and structured failures. **Provider contracts**: normalized model, search, research bundle, source map and conformance records. **Runtime contracts**: immutable packages, capability grants and R0-R4 execution-plane descriptions. Public contracts make interoperability and security review possible without exposing production credentials or the platform's proprietary orchestration and settlement logic. Architecture The diagram describes public trust boundaries, not the production network topology. An Agent must pass runtime conformance before listing; unsupported capabilities fail closed rather

than silently degrading. js 20+ npm 10+ Docker only for container audit exercises Install and verify Run the public frontend locally The public UI can be explored without production secrets. Features that require a hosted Provider, authenticated seller account or managed runtime intentionally remain unavailable in a standalone clone. Product Surface Discover and compare Agents The catalog separates runnable marketplace Agents from external AI tool guidance. Structured fields describe scenario fit, execution mode, risk, evidence and recommended next steps. Inspect

trust and runtime boundaries Agent detail pages distinguish platform-native audited execution, seller-hosted APIs and external handoff. A recognized listing is not automatically a sandbox guarantee. Publish through explicit paths Sellers can submit code artifacts for platform processing or register a seller-hosted HTTPS API. The two paths carry different evidence and trust claims; API-only listings never inherit source-audit claims. Public Integration Contracts The machine-readable contracts live in : Agent Contract v3, Agent Wire v1 and immutable

Runtime Package v1 Universal Runtime planes, capability grants and external resource receipts Model Provider, content-part and conformance contracts Search Provider and Research Bundle v3 Artifact-to-source mapping Seller submission, hosted runtime, market listing and pricing quote See the protocol index for versioning, credential boundaries, R0-R4 semantics and rental accounting. Security and Evidence Platform and seller credentials must remain server-side and must never appear in Wire frames, browser bundles, traces or artifacts. Submitted endpoints and network calls

require SSRF-resistant validation, resolved-address checks, timeouts, response limits and authorization. Audit evidence is bound to versions and content