ZeqMesh Identity — Federated

Equation-based identity, reputation, federation.

• Protocol ID — zeq-identity-mesh
• Category — Identity
• Endpoint — POST /api/auth/mesh/verify
• Auth — api-key
• Rate limit — 30/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Federated identity across Zeq instances. No central authority — your equation produces the same ZID on ANY node. Mesh verification via ZeqLattice coherence.

Signature

Request

POST /api/auth/mesh/verify

Param	Type	Required	Default	Description
zid	string	✓	—	ZID to verify across the mesh.
nodes	array		—	Mesh node URLs to query. If omitted, uses default federation peers.

Response

{ zid, verified, meshNodes, coherenceScore, consensusReached }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "zid": "<value>",
  "nodes": []
}' \
  "https://api.zeq.dev/api/auth/mesh/verify"

Integrate

1. Equation-identity login — derive auth state from a protocol call instead of a static token.
2. Reputation overlay — couple identity scores into the Master Equation via ZRO seeds.
3. Federation bridge — share identity proofs across trust domains using pulse alignment.

Seeds

• Near — wrap /api/auth/mesh/verify in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqMesh Identity — Federated alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqMesh Identity — Federated 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.