Skip to main content

Home

The AISafe changelog tracks notable customer-facing platform and documentation updates. Each version marks the shape of the product at that point in its development, and each release lists the changes that users can act on.

v2 (current)​

Reorganized the documentation and public site.

  • Added the assessment.started and assessment.failed events to webhook subscriptions and to Slack, Microsoft Teams and email notification targets. A failed assessment's event says why it failed and whether the fix is on your side, and a reopened assessment sends both events again for each new run. New webhook subscriptions and notification targets include both events by default. Existing ones keep the events you selected, so add the new events to receive them. See Slack.
  • Documented how an AI agent can register its own AISafe account in https://aisafe.io/auth.md: with an email address through POST /api/v1/auth/signup and POST /api/v1/auth/confirm-email, or with GitHub or Google in a browser. The page also explains when to use the session token and when to use an API key.
  • Made AISafe easier for AI agents to find and use: aisafe.io now publishes an API catalog at /.well-known/api-catalog, an auth.md that explains how to give an agent an API key, and an agent skill. The public API description is at https://docs.aisafe.io/openapi/v1.json, and https://api.aisafe.io/openapi.json redirects there. The API no longer serves /docs or /redoc.
  • Added two-way Jira sync: an organization owner creates a token with POST /api/v1/integrations/connections/{id}/jira-issue-sync-token, and a Jira Automation rule reports issue status changes back to AISafe. See Sync Jira status back to AISafe.
  • Removed GET and PUT /api/v1/organizations/current/model-policy. AISafe chooses the models that run an assessment, and a saved policy never had an effect.
  • Removed GET /api/v1/health/diagnostics and the system:diagnostics API key scope. Keys that list the scope keep working.
  • Removed the unused role field from GET /api/v1/users/me and the profile responses. Use org_role for a member's role in their organization.
  • Changed POST /api/v1/assessments/{id}/revisions, /revisions/upload and /revisions/patch: each now answers 202 with an attachment to poll instead of the revision, and accepts an idempotency_key. A failed attempt needs a new key. See Updating source through the API.
  • Changed POST /api/v1/projects/{id}/revisions and /revisions/upload the same way, and added POST /api/v1/projects/{id}/revisions/patch, which applies a unified diff to a project revision. Poll GET /api/v1/projects/{id}/revision-attachments/{attachment_id}. See Updating project source through the API.
  • Removed target_path from project uploads (/revisions/upload, the resumable upload's project_revision target and aisafe upload --target-path). An uploaded archive is always the project's whole codebase, and a project connected to repositories refuses uploads with project_source_is_repository because its changes come from those repositories. See Updating project source through the API.
  • Rebuilt Black-Box Pentest on the current assessment engine. Each confirmed finding now points to captured HTTP request/response evidence, and every planned test ends with a covered or uncovered result in the run record.
  • Restructured the docs into Home, Services, Platform, and Changelog.
  • Added a Services section with one category per service: Source Code Audit, White-Box Pentest, Black-Box Pentest, Endpoint Monitoring, and Pull Request Review. Each category covers how the service works, how to set it up, and how to read its findings.
  • Reworked Concepts into one page per core noun, from your Account through Organization, Project, Assessment, Finding, Report, and Credits.
  • Kept the dashboard on the Home page: ask how to run a service, browse the services, and explore the platform from one screen.

v1​

The original public documentation.

  • Introduced the Home, Services, Platform, and Changelog tabs.
  • Documented the flat set of features: code audit, pentest, PR review, scheduled scans, monitoring, triage, and reports — each as a single page under Platform.
  • Listed REST API conventions, authentication, errors, and webhooks, with a generated per-endpoint reference.
  • Provided getting-started flows: create an account, run your first assessment, invite your team, and a dashboard overview.

In the move to v2, the flat feature pages became the five standalone Services, scheduled scans and monitoring merged into Endpoint Monitoring, and the public API reference pages were retired from the customer docs.