How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Push Security

Push Security is an AI-native browser security platform that deploys as a lightweight enterprise browser extension to every employee, giving security teams real-time telemetry, autonomous threat-hunting agents, and deep browser visibility across the full identity and browser attack surface. From the browser, Push tracks logins, AI-tool usage, and identity events to stop advanced identity attacks (account takeover, zero-day phishing, ClickFix, malicious OAuth integrations, session hijacking), discover shadow AI and shadow SaaS, harden unmanaged identities, and accelerate incident response. Push exposes a REST API (v1) and webhooks to programmatically administer the platform and forward events to SIEM/SOAR and ticketing systems. Backed by GV and Redpoint Ventures.

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Push Security the way a machine reads it — 6 machine-readable artifacts across 1 API, 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 — Push Security scores 49.3/100 (developing), with a separate agent-readiness read of 33/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 Kin Score How this is scored →
scored 2026-08-03 · rubric v0.9
Composite quality — 49.3/100 · developing
Contract Quality 12.9 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 5.1 / 13
Governance 0.0 / 12
Discoverability 8.7 / 10
Agent readiness — 33/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
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 derived 1.5 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Push Security Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Push Security's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/push-security/"
   title="Push Security on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/push-security.svg"
       alt="Push Security Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Push Security

Each block below is one kind of artifact we hold for Push 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 1

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.

Push Security REST API v1

REST/JSON API to programmatically administer the Push platform (accounts, apps, findings, integrations) plus webhooks for real-time platform events.

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security 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.

Push Security Authentication

apiKey · 1 scheme

SECURITY

Push Security Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Push Security Vulnerability Disclosure

security.txt · contact published

SECURITY

Push Security Trust Center

SOC 2 Type II, ISO/IEC 27001, ISO/IEC 27701, GDPR, Cyber Essentials

SECURITY

Resources

Every other property we hold for Push 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.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 3

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/push-security · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Push Security, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

[email protected] · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.