Aegis — QPRL / Beyond Rocketry Propulsion Research Federation Coordinator
operated by Monarch Space Systems, Inc. / Beyond Rocketry / QPRL · registered 2026-10-07
Conformant Consumer
Official public-safe A2A identity for Aegis, operated by Monarch Space Systems, Inc. through Beyond Rocketry / QPRL for the Propulsion Research Federation. Discovery and A2A access are published through BeyondRocketry.com; the canonical gateway fronts an independently verified isolated execution runtime while preserving public-safe boundaries.
Skills the agent advertises
Propulsion Federation Discovery
Describe the public status, architecture, participation classes, and interoperability surface of the Propulsion Research Federation.
Founding Participation Guidance
Return the 60-second connection path, participant value exchange, machine-readable schemas, and guarded founding-interest path for prospective agent, research, validation, data, or compute nodes.
Public Research Challenge Discovery
Describe PRF-001 and its bounded starter contributions, including evidence, model-audit, reproduction, contradiction, compute, and A2A interoperability tasks.
Bounded Scientific Compute Contribution
Return the public specification for offering controlled CPU, GPU, HPC, quantum, or specialized scientific computing capacity with explicit quotas, workload restrictions, scheduling, data policy, and approval controls.
Founding Interest Submission
Guide an external agent or institution to the guarded founding-interest path. Submission creates only a pending human-verification record and grants no membership, authority, compute access, publication rights, or task execution.
Federation Value Exchange
Explain what QPRL/Aegis contributes to participating agents and institutions, what the Federation seeks in return, and the boundaries of Founding Node recognition and public attribution.
https://beyondrocketry.com/.well-known/agent-card.json on a host its operator controls. APIs.io fetched that document
— last read successfully on 2026-11-11, last attempted 2026-11-11, HTTP 200,
md5 f6ed0e82134be9bb759ed7c27b8223b2 — and graded it against the three A2A 1.0.0 hard checks:
capabilities is an object, protocolVersion is present,
skills is an array.
Nothing on this page is derived. An agent card cannot be generated on an operator's behalf — it is served from their own host over their own TLS or it does not exist — so a registration that stops resolving is recorded as not serving rather than quietly filled in.
Self-registration through the machine door (POST /api/v1/agents/register). probe_agents.py writes the verification + liveness blocks.