System overview

One API, two layers behind it

System overview One API, two layers behind it Your integration · your services, jobs and dashboards · Architecture component Your integration your services, jobs and dashboards paros-server · one REST API, OpenAPI 3.0 · Architecture component · https://app.paros.xyz paros-server one REST API, OpenAPI 3.0 https://app.paros.xyz Salt custody · MPC threshold co-signing · Architecture component · master-signed only Salt custody MPC threshold co-signing master-signed only Hyperliquid · orders, positions, funding · Architecture component · agent-signed Hyperliquid orders, positions, funding agent-signed Salt + Admin routes · org setup, staff tooling, health, webhook intake · INTERNAL SURFACE · present on the server, outside the customer contract · not customer surface Salt + Admin routes org setup, staff tooling, health, webhook intake not customer surface Published reference · same contract, one build behind release · Architecture component Published reference same contract, one build behind release requests and reads master-signed agent-signed serves not for customers INTERNAL SURFACE · present on the server, outside the customer contract Legend Frontend Backend Security External

One door, not two

  • • Every customer operation is an HTTP call to paros-server. There is no separate custody API to integrate
  • • Reads come back through the same call, in the same JSON envelope
  • • Salt appears in the flow as the co-signer behind seven operations, not as an endpoint you call

What the published document still shows

  • • Salt, Admin, health and webhook routes are mounted on the same server and appear in the contract today
  • • Tag cleanup is tracked in issue #879. Until it lands, the customer set is defined by the docs, not by the UI
  • • The machine-readable JSON copies are mounted but not proxied in production, so do not fetch them from the host