Impart Security

Impart Security is a runtime security platform that unifies WAF, API security, and AI/LLM/agent/MCP protection on one inline enforcement engine. It analyzes the full request/response flow — headers, parameters, query strings, and bodies — models API behavior with machine learning, detects anomalies from a learned baseline, and takes inline mitigation actions (alert, block, behavioral rate limiting, deception, tarpits) before requests reach backend systems. Impart also auto-generates OpenAPI documentation from live traffic, integrates with gateways such as Kong, and ships a programmable rules engine managed as code via first-party Terraform and Pulumi providers against its v0 REST API. Founded by Jonathan DiVincenzo, Marc Harrison, and Brian Joe; backed by Madrona, CRV, 8-bit Capital, and Haystack. SOC 2 Type II certified and GDPR ready.

Impart Security is listed with 1 API on the APIs.io network. Tagged areas include Company, Security, API Security, Runtime Protection, and WAF.

Impart Security’s developer surface includes documentation, engineering blog, signup flow, support, authentication, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.4/100 thin ▬ flat Agent 15/100 agent aware Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API

Company Security API Security Runtime Protection WAF LLM Security AI Security MCP Agent Security Kong Governance

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 26.4/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 5.4 / 17

Operational Transparency 0.6 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.8 / 15

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/impart-security/"><img src="https://apis.io/badge/impart-security/card.svg" alt="Impart Security on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 31.6 — up to +13.7 composite points
Operational Transparency scores 5.3 — up to +12.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/impart-security/apis.yml: open an issue on github.com/api-evangelist/impart-security to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Network Edge (CDN, networking, peering, edge compute)	builds-on	46.0	-	-
Infrastructure-as-Code Provider Registries (Terraform, OpenTofu, Pulumi)	builds-on	46.0	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Impart Security v0 REST API

Impart Security's v0 REST management API — programmatically manage specs, API/log bindings, connectors, core rules, rule scripts and recipes, lists, labels, tags, event monitors...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Impart Security Authentication

http-bearer · 1 scheme

SECURITY

Impart Security Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

Compliance

Compliance

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Source (apis.yml)

aid: impart-security
name: Impart Security
description: Impart Security is a runtime security platform that unifies WAF, API security, and AI/LLM/agent/MCP protection
  on one inline enforcement engine. It analyzes the full request/response flow — headers, parameters, query strings, and bodies
  — models API behavior with machine learning, detects anomalies from a learned baseline, and takes inline mitigation actions
  (alert, block, behavioral rate limiting, deception, tarpits) before requests reach backend systems. Impart also auto-generates
  OpenAPI documentation from live traffic, integrates with gateways such as Kong, and ships a programmable rules engine managed
  as code via first-party Terraform and Pulumi providers against its v0 REST API. Founded by Jonathan DiVincenzo, Marc Harrison,
  and Brian Joe; backed by Madrona, CRV, 8-bit Capital, and Haystack. SOC 2 Type II certified and GDPR ready.
url: https://raw.githubusercontent.com/api-evangelist/impart-security/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- crv
- madrona
- 8-bit-capital
- haystack
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Security
- API Security
- Runtime Protection
- WAF
- LLM Security
- AI Security
- MCP
- Agent Security
- Kong
- Governance
image: https://cdn.prod.website-files.com/69c2a371d79849d9c09b537d/6a086ac25135439db8499dee_64b88db668b71259bd9720385d8dde1e_Impart%20Open%20Graph.png
apis:
- name: Impart Security v0 REST API
  description: Impart Security's v0 REST management API — programmatically manage specs, API/log bindings, connectors, core
    rules, rule scripts and recipes, lists, labels, tags, event monitors, and notification templates. Authenticated with a
    scoped API access token issued from the Impart console. This is the API the first-party Terraform and Pulumi providers
    wrap. Reference documentation is behind console authentication.
  humanURL: https://docs.impartsecurity.net/
  baseURL: https://api.impartsecurity.net/v0
  tags:
  - API Security
  - Runtime Protection
  - Rules
  properties:
  - type: Authentication
    url: authentication/impart-security-authentication.yml
  - type: Documentation
    url: https://docs.impartsecurity.net/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
- FN: Impart Security Support
  email: support@impart.security
common:
- url: https://www.impart.ai/blog/rss.xml
  type: BlogRSS
- type: Website
  url: https://www.impart.ai/
- type: DeveloperPortal
  url: https://console.impartsecurity.net/
- type: Documentation
  url: https://docs.impartsecurity.net/
- type: Blog
  url: https://www.impart.ai/resource-center
- type: GitHubOrganization
  url: https://github.com/impart-security
- type: SignUp
  url: https://www.impart.ai/demo
- type: Support
  url: mailto:support@impart.security
- type: PrivacyPolicy
  url: https://www.impart.ai/legal/privacy-policy
- type: Compliance
  url: https://www.impart.ai/
- type: Packages
  url: packages/impart-security-packages.yml
- type: SDKs
  url: packages/impart-security-packages.yml
- type: Authentication
  url: authentication/impart-security-authentication.yml
- type: Conformance
  url: conformance/impart-security-conformance.yml
- type: WellKnown
  url: well-known/impart-security-well-known.yml
- type: DomainSecurity
  url: security/impart-security-domain-security.yml
- type: LLMsTxt
  url: llms/impart-security-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Impart Security API — frequently asked questions

Does Impart Security have an API?

Yes. APIs.io lists 1 API from Impart Security, including Impart Security v0 REST API.

How do I authenticate with the Impart Security API?

Impart Security documents its authentication (http-bearer · 1 scheme). The details are profiled on APIs.io as Impart Security Authentication.

Is the Impart Security API ready for AI agents?

Impart Security has a Kin Score of 26.4 out of 100 (thin) and an Agent Readiness score of 15.1 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/impart-security"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/impart-security/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/impart-security/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.