Build with public EQL data

Developers

EQL Helper publishes a versioned, read-only catalog for community tools. Anonymous access is welcome; optional read keys provide more capacity and a private usage view without granting write access.

API guideEndpoints, examples, paging, caching, formats, errors, and responsible-use guidance.OpenAPI 3.1The canonical JSON service description for generators, API clients, and inspection tools.Catalog metadataCurrent revision, schema version, logical hash, formats, and collection counts.Sources and evidenceUnderstand compatibility profiles, provenance, external references, and known limitations.

Machine-readable contracts

Good integration defaults

Discover records through collection or search responses, then use the exact returned slug.
Store the catalog revision and follow opaque cursors and Link relations without interpreting them.
Cache ETag values and send If-None-Match; use the change feed instead of repeatedly downloading every collection.
Send a descriptive User-Agent with a project name, version, and optional contact URL so we can distinguish and help your tool.
Respect 429 and Retry-After. Ordinary misses and rate limits are guidance, not abuse bans.

Community collaboration

Public APIs are read-only. Signed-in contributors can propose community partners and external references through reviewed forms; public write APIs are intentionally deferred until their authorization and moderation boundaries are ready.