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

2s Security API

The security API from 2s — 16 operation(s) for security.

2s Security API is one of 114 APIs that 2s publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Security. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 16 operations across 16 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://2s.io.

16 operations 16 paths 3 schemas 15 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://2s.io/mcp
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

2s Security API declares 1 security scheme for authenticating requests. An API key is passed in the header as PAYMENT-SIGNATURE (x402Payment).

  • x402Payment — x402 protocol v2: base64-encoded PaymentPayload. Call any paid endpoint without auth to receive a 402 with a multi-network PaymentRequirements envelope. Sign f…

Paths & Operations 16

Across 16 paths, the API surfaces 16 operations — 15 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Security 16
GET
/api/security/attack
Authoritative MITRE ATT&CK (Enterprise) technique lookup
security_attack 4 params → 200400402405500502
GET
/api/security/capec
Authoritative MITRE CAPEC (Common Attack Pattern
security_capec 4 params → 200400402405500502
GET
/api/security/cve
Look up a CVE by id (e.g
security_cve 2 params → 200400402405500502
GET
/api/security/cve-changes
CVE change feed - the CVE records MODIFIED within a time
security_cve-changes 6 params → 200400402405500502
GET
/api/security/cve-search
Find vulnerabilities affecting a product by searching the
security_cve-search 4 params → 200400402405500502
GET
/api/security/cwe
Authoritative MITRE CWE (Common Weakness Enumeration) lookup
security_cwe 4 params → 200400402405500502
GET
/api/security/exploit-availability
Does public exploit code exist for a CVE, and where?
security_exploit-availability 2 params → 200400402405500502
GET
/api/security/http-headers
Fetch a URL and grade its HTTP security headers
security_http-headers 2 params → 200400402405500502
GET
/api/security/ics-advisories
CISA Industrial Control Systems (ICS) advisories
security_ics-advisories 3 params → 200400402405500502
GET
/api/security/ioc-reputation
Threat-intelligence reputation for an indicator of
security_ioc-reputation 2 params → 200400402405500502
GET
/api/security/ip-abuse
AbuseIPDB abuse report for a single IP - the crowd-sourced
security_ip-abuse 4 params → 200400402405500502
GET
/api/security/ip-blacklist
AbuseIPDB bulk blacklist - the most-reported abusive IPs
security_ip-blacklist 6 params → 200400402405500502
GET
/api/security/ip-block
AbuseIPDB subnet (CIDR) check - which IPs inside a network
security_ip-block 4 params → 200400402405500502
GET
/api/security/ip-reputation
Multi-source IP reputation with one combined authority
security_ip-reputation 2 params → 200400402405500502
GET
/api/security/package
Security and provenance for an open-source package
security_package 4 params → 200400402405500502
POST
/api/security/password-exposure
Check whether a password has appeared in known data
security_password-exposure 1 param body → 200400402405500502

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are X402PaymentRequiredV2 (5 properties), Source (3 properties). Each schema is shown below with its type and property counts.

X402PaymentRequiredV2
object
x402 v2 PaymentRequired envelope. Pick any entry from accepts[], sign for that rail, retry with the PAYMENT-SIGNATURE header.
5 properties 2 required
Source
object
Provenance of the data: upstream provider, source URL, and license.
3 properties
CallMeta
object
Per-call meta envelope — endpoint id, cost, caller kind, settlement details.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

2s-io-security-api-openapi.yml Raw ↑

Other APIs 2s publishes across the network.

2s MCP Server
2s A2A Agent
2s Agent API
2s Agriculture API
2s AI API
2s Airport API
2s Aviation API
2s Bank API
2s Barcode API
2s Batch API
2s Bio API
2s Bls API
Where this information came from

This is an independent, third-party profile of 2s Security API, 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.

info@apievangelist.com · 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.