Single Constant Lookup

Operators, constants, equations, experiments — the registry surface.

• Protocol ID — physical-constant
• Category — Data
• Endpoint — GET /api/framework/constants/:key
• Auth — none
• Rate limit — 120/min
• Version — 1.287.6
• Precision — ≤0.1% (KO42-enforced)

What it does

Look up a single physical constant by key.

Signature

Request

GET /api/framework/constants/:key

Param	Type	Required	Default	Description
key	string	✓	—	Constant key: c, G, h, h_bar, k_B, e_charge, m_electron, etc.

Response

{ key, value, unit, name, exact }

Runnable example

curl -sS \
  "https://api.zeq.dev/api/framework/constants/:key"

Integrate

1. Introspection — list what the kernel can compute before authoring a wizard step.
2. Schema generation — feed returned operator definitions into typed bindings in any language.
3. Experiment catalog — wire the response into a UI selector for reproducible demos.

Seeds

• Near — wrap /api/framework/constants/:key in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating Single Constant Lookup alongside a real workload, with pulse-aligned metrics.
• Far — propose Single Constant Lookup as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.