AYDA API Access

📡 Status: Preview Only

AYDA’s Phase 2 API introduces sandboxed inference endpoints, persona‑driven logic, and modular access controls. All functionality is subject to change during the preview period.

🔧 Endpoint Overview

🧠 Persona Switching Logic

AYDA supports dynamic persona switching through the /persona/switch endpoint. Additional routing behavior and enrichment logic are documented under NDA.

🧪 Inference Preview

The /infer endpoint accepts structured requests with persona context and returns high‑level inference results. Detailed traceability features are available under NDA.

💬 Streaming Chat Interface

AYDA’s /chat endpoint enables real‑time persona‑driven conversations using Server‑Sent Events (SSE). This interface is optimized for chatbot UIs, SOC dashboards, and interactive workflows.

Content-Type: application/json
Response: text/event-stream

Optional headers and persona overrides are available under NDA.

⚠️ Notes & Limitations

• All endpoints are sandboxed and rate‑limited
• Persona switching is non‑persistent unless explicitly tagged
• Air‑gapped deployments support offline upgrades and version pinning

🔖 AYDA API Documentation — Public Preview
Last updated: August 2025 · Endpoint structure and behavior may evolve during the preview period.
Additional roadmap details and enrichment logic are available through NDA‑bound materials.

🛡️ AYDA Cyber Defense Modules

AYDA’s modular architecture supports proactive threat detection, forensic analysis, and adaptive response. Below are high‑level examples of how core modules operate in real‑world scenarios.

🚨 Predictive Threat Detection

Goal: Identify and highlight potential threats before they escalate, using enriched behavioral patterns and contextual analysis.
Example: AYDA detects unusual activity across a monitored subnet and recommends segmentation to prevent lateral movement.

🧨 Penetration Testing & Exploit Simulation

Goal: Simulate attacker behavior to validate defensive posture and uncover weaknesses.
Example: AYDA emulates credential‑based attacks, evaluates system responses, and flags missing rate‑limiting or MFA controls.

🛡️ Defensive Hardening & Vulnerability Scanning

Goal: Identify misconfigurations, expired certificates, and third‑party risks across infrastructure.
Example: AYDA returns domain intelligence findings, highlights weak email security posture, and provides a trust score.

🧠 Real‑Time Attack Recognition & Response

Goal: Detect signs of active compromise and recommend containment measures.
Example: AYDA correlates suspicious persistence mechanisms with known threat behaviors and advises isolating affected hosts.

📜 Forensic Trace & Insight Generation

Goal: Produce concise summaries of attack vectors, system posture, and investigative findings.
Example: AYDA identifies lateral movement, correlates beaconing behavior with known threat profiles, and provides a confidence‑scored assessment.

⚠️ Notes & Limitations

• AYDA does not block traffic directly; she recommends containment actions via integrations.
• Zero‑day detection is probabilistic and based on behavioral deviation, not signature matching.
• Red‑team simulations are sandboxed and require explicit opt‑in.
• Traceability features are available in preview and documented under NDA.