Legal notice & privacy commitments.
This page explains who operates AOPX, how the public pilot is hosted, what information is and is not retained, how anonymity is preserved, how benchmark evidence is published, and where responsibility sits when third-party services, registries, partners or external publishers are involved.
Who operates AOPX.
Publisher
AOPX Labs operates AOPX, an experimental evidence-based provider-selection layer for software agents. The current public pilot is consultation-only: AOPX recommends a provider path, the caller executes externally, and the caller may report the resulting production outcome.
Hosting
The public website, API and pilot environment are deployed on third-party infrastructure providers. Availability, network routing, upstream incidents and service interruptions may therefore depend in part on those independent infrastructure providers.
Purpose
AOPX is designed to support provider-selection decisions for software agents using benchmark evidence, policy metadata and reported production outcomes. AOPX does not itself execute the downstream search request, does not resell provider results, and does not act as the publisher of third-party provider content.
Minimal collection. Anonymised public evidence.
No account profile or personal-data database
AOPX does not require a public user account for the current pilot and does not maintain a customer-profile database for pilot callers. AOPX does not intentionally collect names, postal addresses, payment-card data, wallet identifiers, or personal profile fields through the public recommendation flow.
Website analytics
The public website uses Google Tag Manager and Google Analytics 4 for standard audience measurement. Those services are third-party analytics services and may process technical browser or device information according to their own terms and privacy policies. AOPX does not use the public evidence ledger to expose individual visitor analytics.
Anonymity by design
Public production evidence does not expose caller identities. Where a stable technical distinction is required internally, AOPX may use a one-way cryptographic representation such as a SHA-256 hash rather than storing or publishing a directly identifying value. A hash is used as a technical pseudonymous reference, not as a public identity.
No public agent or session identifiers
Public outcome lines and public aggregate statistics do not expose agent names, session identifiers, origin hashes, raw IP addresses, user-agent strings or caller attributes. Public provider identities may also be replaced by neutral aliases such as Provider A and Provider B where publication of the mapping is not necessary.
Public callers stay anonymous
Public evidence is designed around aggregate statistics and anonymised outcome records rather than identifiable caller profiles.
Hashes are not public identities
Cryptographic hashes may be used internally for technical correlation, while unique origin or caller hashes are not published as user identities.
No resale of downstream payloads
AOPX recommends a provider path. The caller performs the provider execution externally. AOPX does not operate as a reseller of the provider's returned search results.
No payment data in the pilot
Billing is disabled during the current public pilot. The AOPX pilot does not collect card or wallet details through the recommendation API.
Independent services remain responsible for their own publications and systems.
Third-party providers, partners and registries
AOPX may reference, integrate with, be listed by, or link to independent providers, registries, marketplaces, workflow platforms, documentation portals, communities and partners. Their websites, listings, documentation, claims, uptime, pricing, security practices and publications remain under their own control.
No responsibility for third-party publications
AOPX Labs is not the publisher of content independently published by third parties or partners and does not assume responsibility for the accuracy, completeness, continued availability, modification or removal of such third-party publications. A link, registry listing, technical integration or interoperability relationship does not constitute endorsement of every statement published by that third party.
External provider execution
When an agent follows an AOPX recommendation, the actual provider call is made outside AOPX in the current consultation model. The downstream provider remains responsible for its own API, payload, licensing terms, content policies, service availability, pricing and processing practices.
AOPX publishes its own benchmark artifacts, policy metadata and reported production evidence. It does not control or republish the full content of independent third-party services and should not be read as guaranteeing third-party statements or outputs.
Frozen artifacts, hashes and clear evidence boundaries.
Hashed benchmark artifacts
Frozen benchmark artifacts are identified with SHA-256 hashes. Separate mission, results, report and matrix artifacts allow a published benchmark claim to be tied to a specific frozen file set without exposing the private decision engine.
Benchmarks are separate from production outcomes
Laboratory benchmarks, tests, shadow runs and replays are not presented as reported production outcomes. Public production evidence is restricted to outcomes reported back after a production recommendation.
Reported does not mean independently verified
A reported production outcome is information returned to AOPX by the caller after execution. AOPX therefore describes these records as reported production outcomes and does not present them as independently verified outcomes.
No fabricated coverage
AOPX does not intentionally present unsupported categories, providers, production history or benchmark conclusions as established facts. Experimental, benchmark and production evidence are kept conceptually separate.
Pilot conditions and limitations.
Public pilot
AOPX is currently operated as a public pilot. Features, supported providers, policies, endpoints and availability may evolve. Billing is disabled during the pilot unless and until commercial terms are published separately.
No universal provider claim
AOPX does not claim that any supported provider is universally superior. Benchmark results apply to the stated protocol, missions, time period and decision path, and may not generalise to every future task.
Availability and warranty
The pilot is provided on an experimental basis. Except where mandatory law provides otherwise, AOPX Labs does not guarantee uninterrupted availability, universal fitness for a particular agent workflow, or error-free operation of independent third-party services.
Questions about legal, privacy or evidence.
For legal, privacy, evidence or publication questions, use the AOPX contact page →