Integrate Q-EaaS from an agent

Q-EaaS supplies high-quality entropy from a quantum random number generator (QRNG) that seeds a standards HMAC-DRBG. Only DRBG-derived bytes, seeds, and ML-KEM key material are served — raw QRNG bits are never exposed. The quantum part is the entropy source; post-quantum resistance comes from ML-KEM.

Discovery documents

Agent manifest:https://api.qeaas.eu/.well-known/agent.json
Tool descriptors:https://api.qeaas.eu/v1/agent/tools
Onboarding manifest:https://api.qeaas.eu/v1/agent/manifest
OpenAPI / Swagger:https://api.qeaas.eu/openapi.json
MCP discovery:https://api.qeaas.eu/.well-known/mcp.json
llms.txt:https://qeaas.eu/llms.txt

How to get a key

Public endpoints (health, random, dice, verify, pubkey) need no key. Developer and KEM endpoints require the header X-API-Key. Keys are admin-minted, revocable, and quota-metered — request one from the operator. Over-limit requests return HTTP 429.

Tool specification

Machine-readable tool descriptors (one per callable endpoint, with JSON Schema) — ready to register in a function-calling or MCP runtime. The onboarding manifest also renders framework-shaped quickstarts via ?profile=http|openai-tools|anthropic-tools|mcp.

Download tool descriptors

Worked example

# anonymous — no key needed
curl -s "https://api.qeaas.eu/random?bytes=32"

# developer endpoint — needs a key
curl -s -H "X-API-Key: $QEAAS_API_KEY" \
  "https://api.qeaas.eu/v1/random/bytes?size=64&format=hex"

# MCP (JSON-RPC 2.0, Streamable-HTTP)
curl -s -X POST "https://api.qeaas.eu/mcp" \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'