Integration Surfaces — How Agents Read and Write Logo

The Logo ecosystem offers different doors per product line. Agent architects should plan around three facts.

1. Reads have two sanctioned patterns

• Logo Objects / REST services (Tiger 3 family): the standard programmatic interface, exposing business objects over REST/SOAP.
• Database usage license (GO 3 / Start 3): licensed direct read access to the ERP database — the pragmatic grounding path at the small-KOBİ tier where API surface is thinner.

An agent grounding layer typically reads orders, stock, recipes/BOM, and customer balances; both patterns support that.

2. Writes have exactly one sanctioned pattern

All writes go through Logo Objects / REST — creating quotes, sales orders, demand slips, purchase orders, ledger transactions. Writing directly to the database breaks version compatibility and vendor support expectations; treat Objects/REST as mandatory for the action layer, not a preference.

For agent design this maps cleanly onto the trust ladder: read-and-draft first (agent proposes the order), write-under-approval second (agent posts it via Objects/REST after human confirmation).

3. Netsis is a second stack

The Netsis line integrates via NetOpenX, not Logo Objects — one product family, two adapters. See Logo Netsis 3.

Per-product notes: Logo Tiger 3 · Logo GO 3 · ecosystem context: Logo Ekosistem Çözümleri — the Partner Program.