Local-first analysis
Static OpenAPI analysis runs locally. The source file is not uploaded for license or entitlement verification.
Technical trust
Security claims should come with boundaries.
Speculynx separates deterministic contract facts, account access, and human decisions. This page states what the product does—and what it does not prove.
01Trust model
Operational boundaries are part of the product.
These statements preserve the existing technical trust contract while moving the page from static HTML to native Next.js.
Deterministic output
Versioned terminal and JSON contracts expose findings, verdicts, diagnostics, and coverage.
Bounded synchronization
Optional dashboard synchronization sends a versioned, sanitized result—not the OpenAPI source.
Exact entitlements
Pro and Agent Security access remain separate. The Suite grants exactly three Agent capabilities.
Signed billing events
Authenticated checkout intent and signed Stripe webhook completion drive billing records and grants.
Credential lifecycle
Agent credentials can be issued, rotated, and revoked. The raw secret is shown once and not stored in recoverable form.
02Analysis boundary
Static evidence is one layer of the security decision.
Speculynx does not prove live IAM, runtime reachability, prompt-injection resistance, absence of vulnerabilities, or safe agent execution. Validate those properties with runtime evidence and human review.
01Finding
A finding is a signal to verify.
02PASS
A PASS is scoped to the evaluated contract model and coverage; it is not a production safety guarantee.
03Disclosure
LOCAL-FIRST REVIEW
Inspect the contract before the agent acts.
Start with a local OpenAPI review, then choose the Agent Security workflow that matches your decision.
Analyze your API