Evidence first. Clear limits. Useful explanations.
Understand how ApiScanner.com separates factual sources, original recommendations, synthetic examples, and unverified claims across its API security resources.
Facts, recommendations, and examples are different
The field notes combine source-supported technical context with practical planning recommendations. Sources establish the specific behavior or framework being discussed. Recommendations describe a proposed way to organize authorized work. Examples use synthetic accounts, routes, and records to make a boundary easier to understand.
An example is not a measured result. A proposed workflow is not a guarantee of security. A report count is not a claim of comprehensive coverage. Those distinctions matter when a page is used in a development ticket, assessment brief, or purchasing discussion.
Prefer primary references
Technical context points to official project documentation or established security guidance. Each long-form article includes one editorial source link in its body. The resource library collects the wider set of primary references used across the site.
Read the versioned documentation that matches the software you operate. The existence of a framework protection or scanner feature does not establish that it is correctly configured in a particular application. Configuration, identity, and scope remain part of the assessment.
No invented product proof
The site does not claim customer counts, measured detection rates, partnerships, certifications, or universal compatibility. It does not publish made-up keyword volumes, tool rankings, or product prices. The free-versus-premium material is an evaluation framework, not a vendor scorecard.
The sample report is explicitly illustrative and has no live target. References to AI products describe possible evaluation contexts, not integrations or endorsements. Human review remains separate from model-generated suggestions.
Keep the review constructive
A useful correction identifies the page, disputed statement, relevant software version, and supporting primary reference. A useful question explains the boundary that is unclear. Avoid including private reports, real customer records, or credentials.
Contact [email protected] with focused feedback. For general orientation, start with the API scanner guide or browse the field notes.