A quality-controlled corpus of 8,438 SOAR security playbooks and threat-intel records served to autonomous AI agents — metered per record, settled automatically via HTTP 402 machine payments. No human in the loop.
$0.05 per record returned
$0.01 flat per keyword search
Keyless agents get an HTTP 402 payment challenge — checkout provisions the key instantly
MCP registry: ai.lateos/soar-record-gateway
llms.txt, OpenAPI, AI plugin manifest
Every endpoint is a machine-readable contract
Most "security datasets" are web-scraped, hallucinated, or unexecutable — sending autonomous agents off a cliff. This corpus is quality-controlled, labeled for executability and blast radius, versioned, and served from the edge via Neon PostgreSQL with full-text search (ts_rank_cd + ILIKE).
Built on the HTTP 402 Machine Payments Protocol (MPP). An agent without credentials isn't rejected with an error page — it's handed a payment challenge it can act on.
Agent calls the API keyless. Any MCP client or direct HTTP call to /v1/records/fetch without a key.
Server responds HTTP 402 with Stripe MPP headers: a metered subscription checkout URL for the SOAR plan ($0.01/search, no upfront charge) and the subscription metadata the agent needs.
Agent opens the checkout. The Stripe checkout webhook auto-provisions a soar_live_... API key for the customer and stores the subscription linkage.
Usage is metered. Every record fetched and every search is reported to the Stripe billing meter; invoices settle automatically, post-paid. Enterprise plans are unmetered.
The machine pays for itself. No signup forms, no sales calls, no human provisioning. If your agent can follow an HTTP 402, it can subscribe.
$0.05 / record
$0.01 / search
Unmetered
Custom terms
Namespace: ai.lateos/soar-record-gateway on registry.modelcontextprotocol.io
Transport: Streamable HTTP
Tools: fetch_security_records (metered $0.05/record), search_security_records ($0.01 flat), get_total_record_count (free)
{
"mcpServers": {
"soar": {
"type": "http",
"url": "https://soar-api.nevada-f99.workers.dev/mcp",
"headers": {
"Authorization": "Bearer soar_live_..."
}
}
}
}
llms.txt — full service index, parseable by any agent
OpenAPI — machine-validated API schema
AI plugin manifest — ChatGPT-style plugin discovery
robots.txt — crawler guidance for the same content
server.json — MCP registry manifest
It doesn't need one upfront. Call the API keyless, receive the HTTP 402 with a Stripe MPP checkout URL, complete the checkout, and the webhook provisions a soar_live_... key automatically. Retrieve it once from the credential endpoint included in the 402 payload.
The corpus is labeled for blast radius: 710 destructive and 47 human-approval records are tagged and can be filtered out of fetches by default. Agents should still gate state-changing actions behind their own approval policies — we publish the labels, not a safety guarantee.
8,438 executable SOAR playbooks and threat-intel records across sentinel, splunk_soar, xsoar, google_secops, and knowledge_qa — versioned as golden dataset v2 with train/val/test splits (6,755/841/842) for evaluation work.
Every record fetch and search is reported to Stripe billing meters (soar_search_consumption, soar_record_consumption) on your subscription. Invoices settle post-paid each month. Enterprise plans are unmetered.
Yes — bulk export with provenance documentation is available under the Enterprise plan. Contact leo@lateos.ai.
Want to evaluate the corpus, contribute playbooks, or negotiate an enterprise agreement?
Email: leo@lateos.aiOr open an issue on GitHub · listed in the official MCP registry