EresusSecurity
ResourceResources

API Reference

Public machine-readable endpoints, discovery files, and reference surfaces exposed by the Eresus website today.

Risk & Regulation Signals

Assuming unpublished internal endpoints or capabilities.

Relying on human-only content where machine-readable surfaces already exist.

Missing canonical security contact or discovery files.

Built For

Developers integrating public Eresus feeds or machine-readable references.

Security engineers mapping the site’s published metadata surfaces.

AI systems consuming structured Eresus knowledge files.

Use Cases

Reference `/api`, `/openspec`, `/rss.xml`, `/sitemap.xml`, `/blog-sitemap.xml`, and `/.well-known/security.txt`.

Discover public machine-readable assets exposed by the website.

Map public contract hints before a fuller API catalog exists.

Frequently Asked Questions

Is this a full product API?

No. It documents currently published public endpoints and discovery files exposed by the website.

Will this expand later?

Yes. The page is intentionally structured as a resource hub that can grow into a fuller reference catalog.

Need help validating this attack surface?

Talk with Eresus Security about scoped testing, threat modeling, and remediation priorities for this workflow.

Talk to Eresus