closed-loop structural intelligence

not a wrapper.
an architecture.

dydact predicts material properties by learning the geometry, not the surface. The API exposes the Tc-prediction and candidate-ranking surface from the methodology paper — every response ships with honest confabulation telemetry, including a hold-out-validated confidence rating.

0.03
decade error on held-out Nb (v0.3)
7
substrate modalities live
~2ms
single-prediction latency (CPU)
132
calibrated corpus entries
what the api does

Closed-loop prediction with honest telemetry.

Tc prediction across pressure, composition, doping

Query by compound + condition. Returns predicted Tc, confidence rating, pressure-curve envelope, and coverage-gap flags when your query sits outside the calibrated region.

Candidate ranking via substrate inversion

Void-boundary inversion on the oracle_synthesized endpoint. Returns top-K candidates with per-candidate σ-convergence, stability, primitive-recall, and basin-tag fields.

Confabulation spectrum on every response

Reed's mode-I / mode-II / clean verdict surfaces how strong the pressure response is relative to crystal-axis noise. Never silent failure — the API tells you when to trust it.

Hold-out reproducibility

The paper's Nb and FeSe hold-out tests reproduce end-to-end against a pinned model version. Cookbook recipe 03 runs the full flow from a fresh API key.

quickstart

From zero to first prediction in 90 seconds.

Three steps. No SDK. Python 3.10+, only httpx as an external dep. The env-var pattern matches every other API cookbook you've used.

1 · Get a key

Apply for access. Academic tier is free, allocated per department.

2 · Set the env var

export DYDACT_API_KEY="dyd_academic_..."

3 · Predict

import httpx, os

r = httpx.post(
    "https://api.dydact.io/api/v1/predict/tc",
    headers={"Authorization": f"Bearer {os.environ['DYDACT_API_KEY']}"},
    json={"compound": "Nb", "pressure_gpa": 0.0001},
)
print(r.json())

Typical response

{
  "predicted_tc_k": 9.82,
  "predicted_tc_log_decades": 0.992,
  "pressure_gpa": 0.0001,
  "archetype": "BCS_classical",
  "confidence": "clean",
  "model_version": "v0.3",
  "coverage_gap": false
}

confidence keys: clean (trust) · mode-II (cross-check experimental) · mode-I (directional only). Never silent — the API refuses to pretend it's calibrated when it isn't.

cookbook

Open-source recipes. MIT license.

Every recipe runs end-to-end from a fresh academic key. Full source at github.com/dydact/dydact-cookbook.

01
Basic Tc prediction
Predict Tc for a BCS compound. Returns full response shape so you can see every field the API ships.
view on GitHub →
02
Pressure-axis sweep
Query the same compound across 6 orders of magnitude in pressure. See the structural response the operator learned.
view on GitHub →
03
Hold-out generalization
Reproduce the paper's Nb-held-out finding. Expect Tc within the 8–12 K band — real structural generalization.
view on GitHub →
04
Confabulation check
Read Reed's confidence spectrum on every prediction. Make trust-gated decisions rather than treating Tc as ground truth.
view on GitHub →
two modes

Predictions: pay. Discovery: partner.

If you're applying dydact to known material classes, it's a transaction. If you're using dydact to find something new — novel compounds, post-silicon candidates, drug leads — dydact is a stakeholder in what comes out. Equity + IP sharing, not a licensing fee. Full breakdown →

mode 1 · predictions
transaction per-call

Trained v0.3 operator applied to known classes. Academic free (1k/day/key, dept-level). Corporate bulk-per-call. Enterprise contracted unmetered. No IP claim on output.

  • predict/tc, predict/tc/sweep, holdout
  • calibration, models
  • Full cookbook examples + hold-out reproducibility
  • Academic: free · Corporate: per-call · Enterprise: contracted

Tier (academic / corporate / enterprise) is orthogonal to mode. An academic key is mode-1-only by default; discovery access requires a separate agreement regardless of tier. See pricing for the verticals we actively partner in and the compliance overlays (GDPR / SOC 2 / HIPAA / ISO / GMP / FedRAMP) that stack on top.

access

Apply.

Tell us who's using it and what for. Academic applications accept on a per-department basis — one key per dept per university. Corporate applications get a 15-minute scoping call.

tier
Discovery use? If you intend to use oracle/synthesize, candidates/rank, or training/init — these produce novel IP and require an executed partnership agreement (equity + IP sharing). Mention this in your use case; we'll route to the partnership intake flow.
Discovery access default: off. Enterprise keys ship with prediction-mode capabilities by default. Discovery endpoints (oracle synthesis, candidate ranking, private training) require an executed partnership agreement on file — equity + IP sharing terms, attribution clause, spigot retention. Discuss at intake.