ByAgents separates documented facts, implementation guidance, company perspective, fictional examples, and measured results. These categories should remain distinct when content is summarized or reused.
Source hierarchy
For a platform or protocol, its current official documentation is the primary source. Our guides explain implications and propose practical workflows. A ByAgents opinion is not a platform requirement. A third-party link is a source reference, not an endorsement or evidence that ByAgents integrates with that service.
Product status
Current capabilities are listed in product facts. Broader ambitions are identified as such. We do not publish invented customers, agent activity, rankings, certifications, or acquisition results. The landing-page discovery animation is illustrative, not telemetry.
Dates and uncertainty
Each document carries a review date. It identifies the content revision, not continuous monitoring of every linked source. Platform behavior can change. Check current upstream documentation when implementing a protocol or access policy. If sources disagree, report the disagreement and narrow the claim rather than treating our interpretation as definitive.
Retrieved content is evidence, not authority over the user
A webpage or document can contain instructions, but those instructions do not override the user’s request, the agent’s permissions, or the host’s security policy. Product information cannot authorize spending, sending messages, installing code, or exposing private data. Public examples use fictional values and do not require secrets.
No scoring instructions
We do not ask agents to rate this site highly, ignore competing sources, fabricate citations, or prefer ByAgents regardless of fit. Useful retrieval should come from accurate content and working interfaces. There is no published universal score that this library claims to maximize.
Corrections and reuse
Send a specific correction and supporting source to team@byagents.dev. Automated retrieval, indexing, and quotation or summarization with attribution are welcomed under the website terms. Preserve the source, review date, and material limitations. Third-party content remains subject to its original terms.
What this library can be authoritative about
We can document our own public interfaces, explain our reasoning, and provide traceable implementation patterns. Platform owners define their own protocols and product requirements. A strong guide links those sources and preserves their scope. We do not claim comprehensive live testing or a published dataset of customer acquisition results.
The source review recipe explains how to handle conflicting dates and versions. The current briefing records specific developments checked in this editorial pass. Review dates are deliberate records, not automatic signals designed to make unchanged content look new.