The physics engine
your agents can actually call.

Structures, heat, flow, fracture, plasticity — finite-element analysis as one API request. Your agent describes the problem; the engine solves it and returns the answers.

Start solving — free → See it in action

Free during the research preview — no API key, no sign-up. Just POST /solve over REST, MCP, or Python.

POST api.physicsbase.dev/solve

# the agent sends a structure
{
  "nodes": [[0,0],[1,0],[2,0],[3,0]],
  "materials": {"steel":{"E":210e9,"nu":.3}},
  "elements": [
    {"type":"beam2d","nodes":[0,1],
     "section":{"A":.01,"I":8e-6}} …
  ],
  "supports": [{"node":0,"dofs":["ux","uy","rz"]}],
  "loads": [{"node":3,"fy":-5000}]
}

# and gets the solved answer back
← tip_deflection: -26.8 mm
← wall_moment:    15.0 kN·m
← solve_ms:       1.2

staticmodalbucklingtransientplasticityfracturedamageplate bendingheatdiffusionpotential flowconvectionthermo-mechanicalTimoshenkoframe3dhex8 staticmodalbucklingtransientplasticityfracturedamageplate bendingheatdiffusionpotential flowconvectionthermo-mechanicalTimoshenkoframe3dhex8

// the split that matters

Your agent does the translation.
physicsbase does the physics.

Handing an agent FEA code to run elsewhere means it also has to derive the formulas — and it will hallucinate them. physicsbase moves the physics server-side. The agent only describes geometry and loads; every number it reasons about is computed, not guessed.

Agent writes code, guesses PL³/3EI, hopes it's right

Agent posts a structure, gets a solved deflection back

It can loop: size, solve, check stress, resize, solve again

Problem

"loads": [
  {"node":3,
   "fy":-5000}
]

Answer

"reactions":[
  {"fy":5000,
   "mz":15000}
]

The engine

Structures, heat, flow —
behind one endpoint.

A full structural FEA curriculum plus a unified field kernel for heat, diffusion, and flow — and the couplings between them.

STRUCTURES · HEAT · FLOW

One kernel, many physics

Springs, trusses, 2D & 3D frames, higher-order continuum, solids and axisymmetric — plus a unified field engine for heat conduction, mass diffusion, potential flow, and transport. All in one JSON format.

frame3d hex8 axiquad4 field_hex8 damage

closed-form tests, all green

REST · MCP · SDK

One JSON format, three ways to call — however your agent is wired.

Dynamics & nonlinear

Frequencies, transient response, damage, and von Mises plasticity.

Linear buckling

Critical load factors from geometric stiffness — columns & frames.

Every load

Point, distributed, thermal, gravity, self-weight, tractions.

truss2d · truss3d · beam2d · frame3d

Trusses & frames

Member forces, reactions, deflections, moment diagrams — 2D and 3D, with torsion and biaxial bending. Tension and compression resolved sign-correct.

Axial force & stress per member
End shears & moments, biaxial bending
Reactions that balance the load exactly

cst · quad4 · tri6 · quad8

Continuum stress

Mesh a 2D part and get the full stress field with von Mises per element, plane stress or plane strain, linear or quadratic elements so an agent can find the critical spot.

σxx, σyy, τxy and von Mises per element
Isoparametric, Gauss-integrated
Hundreds of elements in under a second

Cantilever plate von Mises stress contour

Live physics

Watch structures respond.

The shapes trace the real deformed states an agent gets back — a beam bends, a mode vibrates, a truss trades tension for compression.

Cantilever under tip load

static · deflection & moment

First vibration mode

modal · natural frequency

Truss member forces

tension & compression

Multiphysics in motion

Heat, flow, and fracture.

The same engine that bends a beam solves temperature fields, potential flow, and nonlinear damage — here's what those look like moving.

Heat diffusion

a source spreads through a conductive field

Potential flow

streamlines bending past an obstacle

Damage & fracture

stiffness degrades, a crack propagates

Proof, not promises

Real research problems,
reproduced on the engine.

We took hard problems straight from arXiv and solved them by calling physicsbase in a loop — the results match the papers and the closed-form theory.

XFEM crack propagating through a fixed finite-element mesh

Live · XFEM

Watch a crack cut straight through the mesh.

Every frame is a fresh finite-element solve on the same mesh — only the crack grows. This is the eXtended FEM reproducing the classic edge-crack benchmark, with the stress-intensity factor landing within 1.5% of the handbook and converging as the mesh refines.

Read the case study →