Aikido Security
Aikido Security is a developer-first all-in-one application security platform that consolidates SAST, SCA, secret detection, container scanning, IaC scanning, CSPM, DAST, API security, malware detection, cloud posture, and AI pentesting into a single product designed for engineering teams. Aikido exposes a public REST API at apidocs.aikido.dev covering issues, code repositories, cloud resources, containers, domains and APIs, compliance (SOC2, ISO 27001, NIS2, CIS), custom SAST rules, AI pentesting, task tracking, webhooks, user and team management, Zen app-protection configuration, and activity logging.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Aikido Security the way a machine reads it — 21 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Aikido Security scores 44.8/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Aikido Security
Each block below is one kind of artifact we hold for Aikido Security. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Aikido Security Clouds API
The Clouds API from Aikido Security — 7 operation(s) for clouds.
Aikido Security Code Repositories API
The Code Repositories API from Aikido Security — 4 operation(s) for code repositories.
Aikido Security Compliance API
The Compliance API from Aikido Security — 5 operation(s) for compliance.
Aikido Security Containers API
The Containers API from Aikido Security — 3 operation(s) for containers.
Aikido Security Custom Rules API
The Custom Rules API from Aikido Security — 2 operation(s) for custom rules.
Aikido Security Domains API
The Domains API from Aikido Security — 3 operation(s) for domains.
Aikido Security Issues API
The Issues API from Aikido Security — 6 operation(s) for issues.
Aikido Security Teams API
The Teams API from Aikido Security — 2 operation(s) for teams.
Aikido Security Users API
The Users API from Aikido Security — 2 operation(s) for users.
Aikido Security Webhooks API
The Webhooks API from Aikido Security — 2 operation(s) for webhooks.
Aikido Security Workspace API
The Workspace API from Aikido Security — 2 operation(s) for workspace.
Aikido Security Zen API
The Zen API from Aikido Security — 2 operation(s) for zen.
Scroll within the panel for all 12 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Aikido Security Public REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aikido Security Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Aikido Security Finops
FINOPSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Aikido Security — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aikido-security · machine-readable index on apis.io