Skip to content
Integrations · Local API

Connect Neo to your systems, exposing nothing.

The server only answers on your computer, requires a token and checks the Host header. Your systems ask for equations, batches, OCR and chemistry through the same API the InDesign plugin uses.

curl
curl -s http://127.0.0.1:8790/v1/saude

curl -s -H "Authorization: Bearer $TOKEN" \
  -X POST http://127.0.0.1:8790/v1/eps \
  -d '{"mathml":"\\frac{a}{b}"}' -o eq.eps
The problem

Integrating usually means opening the network

  • Exposed service

    For a system to request an equation, a server has to be published.

  • Data leaving

    Equations and documents travel outside the institution.

  • Systems without integration

    Reports and internal platforms don't talk to the editor.

Neo's local API talks only to your computer.

Examples

In the language you use

  • Port and token read from the session file
  • Full OpenAPI specification
  • Errors with code and message
const r = await fetch("http://127.0.0.1:8790/v1/eps", {
  method: "POST",
  headers: { "Content-Type": "application/json", Authorization: `Bearer ${token}` },
  body: JSON.stringify({ mathml: "x^2 + y^2 = r^2" }),
});
Security

Protections on by default

  • Only on the computer

    Answers only on this computer; nothing is exposed on the network.

  • 64-character token

    Generated at every start and stored with user-only permission.

  • Against address spoofing

    Host header checked; web origins only if you allow them.

Routes

Main routes

/v1/eps
Generates the equation with style and color options
/v1/lote
Several equations at once, inside the root folder
/v1/ocr
Recognizes the equation in an image (app)
/v1/quimica
Structure by name (app)
/v1/editar, /v1/vinculos
Editing in the app and file tracking
/v1/saude
Server status and capabilities, no token

Shall we talk about your production?

Tell us what your team publishes and we'll recommend the right plan and rollout.