Salitech API (Planned)

Salitech API (Planned)

The planned central backend API serving as the authoritative gateway between customer AI agents and the central Salitech database.

Status PLANNED

Endpoint https://api.salitech.de

Host Server production-01

Client Access Customer AI Agents

---

Architectural Role

Salitech API decouples autonomous customer agents from direct data storage layers. It enforces tenant isolation, validation, business rules, and audit logging.

┌────────────────────────────────────────┐
│ Customer Agent (AI Runtime)            │
└──────────────────┬─────────────────────┘
                   │ HTTPS (Token Auth)
                   ▼
┌────────────────────────────────────────┐
│ https://api.salitech.de                │
└──────────────────┬─────────────────────┘
                   ▼
┌────────────────────────────────────────┐
│ Salitech API Gateway                   │
└──────────────────┬─────────────────────┘
                   ▼
┌────────────────────────────────────────┐
│ Service Layer (Business Logic)         │
└──────────────────┬─────────────────────┘
                   ▼
┌────────────────────────────────────────┐
│ Repository Layer (Data Access)         │
└──────────────────┬─────────────────────┘
                   ▼
┌────────────────────────────────────────┐
│ PostgreSQL Database                    │
└────────────────────────────────────────┘

---

Strict Security Requirements

1. Zero Direct DB Access: Customer agents must never be given direct connection strings, credentials, or network paths to PostgreSQL.
2. Layered Architecture: Requests must flow through Controller -> Service Layer -> Repository Layer -> PostgreSQL.
3. Agent Authentication: Every agent authenticates via cryptographic bearer tokens / API keys scoped to the customer’s organization ID.
4. Rate Limiting & Telemetry: Enforced per-agent quotas and complete request/response audit trails.