Escape
Escape was founded in 2020 after one of our co-founders experienced a cyberattack and saw firsthand how vulnerable exposed APIs can be. Driven by a belief in the power of AI to transform cybersecurity, we built a platform that emulates hacker behavior to identify vulnerabilities before they can be exploited. Escape is a DAST (Dynamic Application Security Testing) platform that helps you document all your APIs, detect complex business logic flaws across modern applications like APIs, SPAs, and Microservices, and seamlessly integrate security into your CI/CD pipeline.
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 Escape the way a machine reads it — 27 machine-readable artifacts across 20 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 — Escape scores 44.1/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 Escape
Each block below is one kind of artifact we hold for Escape. 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 20
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.
Escape Asm API
Attack Surface Management Trigger and manage ASM discovery scans on your attack surface. See [our documentation](https://docs.escape.tech/documentation/asm/) for more details.
Escape Assets API
Manage every discovered Assets. The public API provide basic CRUDs operations for all available assets. See [our documentation](https://docs.escape.tech/documentation/asm/asset-...
Escape Audit API
List audit logs. The public API provides endpoints to list audit logs. See [our documentation](https://docs.escape.tech/documentation/enterprise/audit-logs/) for more details.
Escape Beta API
Beta These endpoints are in beta and are subject to change.
Escape CustomRules API
Manage your custom rules. The public API provides basic CRUDs operations to manage custom rules. See [our documentation](https://docs.escape.tech/documentation/dast/custom-rules...
Escape Emails API
Read scan inbox emails. The public API provides endpoints to list inbox emails and read their raw content without exposing storage links.
Escape Events API
Manage events. The public API provides basic CRUDs operations to manage events.
Escape Integrations API
Manage 3rd party integrations. The public API provide basic CRUDs operations for all available integrations. See [our documentation](https://https://docs.escape.tech/documentati...
Escape Issues API
Manage issues. Identify, prioritize, and remediate the security issues and sensitive data exposures uncovered during ASM and DAST scanning See [our documentation](https://docs.e...
Escape Jobs API
Asynchronous jobs. Trigger export jobs and poll for completion and artefacts.
Escape Locations API
A Location is a proxy environment through which Escape sends requests. The public API provide basic CRUDs operations for your private locations. See [our documentation](https://...
Escape Profiles API
A Profile is a configuration for the DAST scanning feature. It includes various parameters such as authentication details, environment settings, a schema... Profiles allow you t...
Escape Projects API
Projects Management The public API provides CRUDs operations to manage projects.
Escape Roles API
Roles Management The public API provides CRUDs operations to manage roles.
Escape Scans API
A Scan is a run of the DAST or ASM scanning feature on an profile (DAST/ASM). With the public API, you can trigger scans, track their status, and retrieve their results. See [ou...
Escape Statistics API
Organization Statistics High-level organization security posture statistics.
Escape Tags API
Manage tags. The public API provides basic CRUDs operations to manage tags.
Escape Upload API
Upload helper for Escape Platform. The public API provides endpoints to upload files to the platform.
Escape Users API
Users Management The public API provides CRUDs operations to manage users.
Escape Workflows API
Workflows Management The public API provides CRUDs operations to manage workflows.
Scroll within the panel for all 20 ·
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).
Escape Public 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.
Escape Plans Pricing
PLANSRate 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.
Escape 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.
Escape Finops
FINOPSSecurity Posture 2
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 Escape — 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.
Documentation 1
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 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
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/escape · machine-readable index on apis.io