Hacware
HacWare is an AI-powered security awareness training and phishing simulation platform that helps organizations reduce human-factor cyber risk. Its RESTful Security Awareness API lets partners and developers embed HacWare into their own products: schedule and manage AI-generated phishing simulations (clickable link, attachment, direct response, and SMS), enroll users in micro-training courses, lesson plans and quizzes, run dark web breach reporting and human-risk assessments, manage users, groups and Microsoft 365 security groups, and operate a multi-tenant partner/customer hierarchy with compliance evidence retrieval. The API is documented with apiDoc and exposes 114 operations across Phishing, Training, Reporting, User, Group, Compliance, and Multi-Tenant surfaces. HacWare is a Techstars portfolio company.
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 Hacware the way a machine reads it — 14 machine-readable artifacts across 11 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 — Hacware scores 43.1/100 (thin), with a separate agent-readiness read of 37/100 (agent aware). 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 Hacware
Each block below is one kind of artifact we hold for Hacware. 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 11
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.
Hacware Admin API
The Admin API from Hacware — 3 operation(s) for admin.
Hacware Compliance API
The Compliance API from Hacware — 7 operation(s) for compliance.
Hacware Compliance-Tenant API
The Compliance-Tenant API from Hacware — 5 operation(s) for compliance-tenant.
Hacware Customer API
The Customer API from Hacware — 6 operation(s) for customer.
Hacware Email-Tenant API
The Email-Tenant API from Hacware — 1 operation(s) for email-tenant.
Hacware Group API
The Group API from Hacware — 12 operation(s) for group.
Hacware Multi-Tenant API
The Multi-Tenant API from Hacware — 5 operation(s) for multi-tenant.
Hacware Phishing API
The Phishing API from Hacware — 17 operation(s) for phishing.
Hacware Report API
The Report API from Hacware — 16 operation(s) for report.
Hacware Training API
The Training API from Hacware — 28 operation(s) for training.
Hacware User API
The User API from Hacware — 9 operation(s) for user.
Scroll within the panel for all 11 ·
Security 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 Hacware — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hacware · machine-readable index on apis.io