We count page visits with Google Analytics to see which pages are read. Nothing is stored until you accept, and we never store search queries. Privacy.
Aribot is your security teammate. Ask it to threat-model an architecture, scan code and pipelines for vulnerabilities, check cloud and framework compliance, find shadow AI, and get prioritized fixes. Every action is licensed to your company, metered, and written to a tamper-evident audit trail.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aribot-security-agent","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Generate a threat model — Create a threat model from a normalized architecture (ReactFlow nodes + edges). Aribot stores the components and generates the threats. Returns the diagram id.
Run a code security scan — Start (or re-run) a code-security scan for an existing scan/repository in your scope. Returns a poll pointer; results include SAST, secrets, deps, pipeline review and the traceability matrix.
Run a platform / compliance scan — Run a cloud/platform or compliance scan against an account or diagram in your scope (async). scan_type ∈ platform|compliance|pipeline|sbom. Returns a task id to poll.
Plan a remediation (dry run) — Compute a remediation plan for a threat or finding without applying it (dry run). Runs Aribot's governed remediation checks and returns the proposed steps.
Apply a remediation (governed) — Apply a remediation for real (mode=live). Goes through Aribot's governance checks (attack-path reachability, autonomy policy and the approval flow). If your policy requires approval it returns 'requires_approval' rather than acting.
Get the traceability matrix — Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics.
Get a diagram summary — Summary of a diagram: threat counts by severity, risk value, compliance and framework coverage.
List threat-model diagrams — List your company's threat-model diagrams (id, name, last update), newest first, optionally filtered by part of the name.
Get diagram insights — Code-security metrics for a diagram: the threat → finding → control metrics of its latest code-security scan. code_scan is null when the diagram has no scan yet.
Verify threats in code — Verify whether modelled STRIDE/LINDDUN threats are mitigated in a scan's uploaded code or AST. If threat_id is provided, returns synchronous verdict; otherwise dispatches batch verification across all diagram threats.
Discover Shadow AI & APIs — Scan connected repositories and network traffic for unmanaged LLMs, foundational model endpoints, vector databases, agent frameworks, and leaked API keys (async).
kind ← A2A Agent Card
name ← A2A Agent Card
summary ← A2A Agent Card
version ← A2A Agent Card
description ← A2A Agent Card
homepageUrl ← A2A Agent Card
publisherUrl ← A2A Agent Card
publisherName ← A2A Agent Card
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
2 mo ago · declared · summary → "Aribot is your security teammate. Ask it to threat-model an architecture, scan code and pipelines for vulnerabilities,
2 mo ago · declared · description → "Aribot is your security teammate. Ask it to threat-model an architecture, scan code and pipelines for vulnerabilities,
2 mo ago · declared · publisherName → "Aristiun (Ayurak)"
2 mo ago · declared · publisherUrl → "https://ayurak.com"
2 mo ago · declared · homepageUrl → "https://developer.ayurak.com"
2 mo ago · declared · version → "1.0.0"
2 mo ago · declared · protocols → ["a2a"]
Get compliance framework coverage
— Get control-mapped coverage percentages, gap counts, and mapped controls for EU AI Act, DORA, NIST AI RMF, ISO 27001, SOC 2, etc.
Company compliance status rollup — Company-level compliance posture: per-framework posture from the daily cloud scans (checks passed/failed, controls tested/failing), plus threat and control metrics from code scans. Pass `framework` (e.g. 'ISO 27001') to get that framework's most-failing controls. Rates are percentages (0-100).
Generate architecture & threat model from prompt — Generate a multi-tier cloud/AI architecture and auto-synthesize STRIDE/LINDDUN threat models, security requirements, and regulatory control mappings directly from a natural-language description. Runs in the background (a few minutes); returns the name the diagram is saved under.
Audit architecture or scan against AI regulations — Audit an architecture diagram or code scan against statutory AI governance frameworks (EU AI Act 2024, EU DORA 2022, NIST AI RMF 1.0, ISO 42001). Evaluates article-by-article conformity, satisfied controls, open gaps, and generates actionable remediation guidance.
Get code-security findings — Findings from a code-security scan (SAST, secrets, dependencies): title, severity, file and line, CWE/OWASP category, status and the recommended fix. Latest completed scan when scan_id is omitted.
Get shadow-AI discoveries — AI usage found in your code and network traffic: provider, service type, model, endpoint, where it was found, risk level, classification and whether a hard-coded key was seen. Company-wide, or one scan with scan_id.
Get governed AI agents — Your governed AI-agent fleet: each agent's id, name, cohort, whether it is active, its execution state (running, held, suspended), deviation score and the reason for any hold. Totals by state.
Get self-healing activity — Remediation (self-healing) history: each planned or applied fix with its threat, rule, resource, mode (dry run or live), status and outcome, plus whether autonomous live remediation is switched on for your company.
List ticket destinations — Trackers, routes and destinations this caller may send threats to (no credentials).
Send threats to a tracker — Send 1-50 threat report entries to the tracker their route points at (or `destination`). One ticket per threat per report; a repeat returns already_filed. dry_run=true returns the exact tickets without sending; a preview with public_repository=true goes to a public repository, visible to anyone. Error codes: permission_missing, role_missing, destination_not_found, already_filed, rate_limited, assignee_unmapped, no_route, no_entry, not_found, invalid, no_company, tracker_error, filed_unrecorded,…
Get tickets for threats — Tickets (tracker, number, state, assignee) for the given threat entries, or for a diagram.
Sync ticket status now — Pull the current state and assignee of this company's open tickets (max 50 per call, time-boxed). Returns {checked, changed, errors, remaining}; remaining > 0 means call again to continue. Error codes: permission_missing, role_missing, destination_not_found, already_filed, rate_limited, assignee_unmapped, no_route, no_entry, not_found, invalid, no_company, tracker_error, filed_unrecorded, outcome_unknown, not_attempted, not_configured, tracker_unreachable, unsupported. filed_unrecorded and outc…
Assign a threat — Set the owner and due date of a threat entry; the linked ticket follows. Error codes: permission_missing, role_missing, destination_not_found, already_filed, rate_limited, assignee_unmapped, no_route, no_entry, not_found, invalid, no_company, tracker_error, filed_unrecorded, outcome_unknown, not_attempted, not_configured, tracker_unreachable, unsupported. filed_unrecorded and outcome_unknown mean the ticket may already exist in the tracker; not_attempted means the item was not sent.
Comment on a pull request about threats — For a completed pipeline scan of a pull request: post, or update, one comment per threat whose linked code the pull request changes. A re-run with nothing changed makes no calls. Returns each comment's status (posted, updated, skipped with the reason, failed). Public repositories are skipped with the reason 'public repository'. Error codes: permission_missing, role_missing, destination_not_found, already_filed, rate_limited, assignee_unmapped, no_route, no_entry, not_found, invalid, no_company,…