الانتقال إلى المحتوى الرئيسي

Java SDK — zeq

JDK 17+ client. Uses java.net.http.HttpClient from stdlib + Jackson for JSON. Same wire format as every other SDK.

Install​

<!-- Maven -->
<dependency>
  <groupId>org.zeq</groupId>
  <artifactId>zeq</artifactId>
  <version>1.287.5</version>
</dependency>
// Gradle
implementation("org.zeq:zeq:1.287.5")

First call — public, no key​

import org.zeq.Zeq;

var p = Zeq.pulse();
System.out.printf("Zeqond %d · phase %.3f · R(t) %s%n",
    p.zeqond(), p.phase(), p.rT());

Authed call — Zeq.compute()​

import org.zeq.ZeqClient;
import org.zeq.ComputeRequest;
import java.util.Map;

var zeq = ZeqClient.fromEnv();          // reads $ZEQ_KEY

var r = zeq.compute(ComputeRequest.builder()
    .operators("KO42", "QM5", "GR40")
    .domain("cross")
    .inputs(Map.of("t", 0))
    .build());

System.out.printf("%s %s ± %s%n", r.value(), r.unit(), r.uncertainty());
System.out.println("zeqProof: " + r.zeqProof());
System.out.println("compliance: " + r.compliance().standardsAligned());

r.compliance() is the ZeqCompliance v1 envelope returned on every call.

Why Java here​

  • Enterprise services. Drop into a Spring Boot app — ZeqClient is bean-friendly and reuses the JDK's HttpClient for connection pooling.
  • Banking and insurance. A compute envelope is a SOC 2 / SOX-ready audit row; the JVM ecosystem's audit-log wiring snaps in directly.
  • Android. The same artifact runs on Android; pair with the Web JS observer for a hybrid mobile app.

Compose with​

Source​