API & integration reference
How your engineers connect to Yebo OS — the integration model, auth approach, and resource concepts. A high-level overview; full per-tenant endpoint docs are provided at onboarding.
Integration model
Yebo OS connects to your stack through the Integration Layer — encrypted connectors for legacy ERPs, modern SaaS APIs, and IoT/event streams — normalizing everything into the knowledge graph. Integration is additive; you keep your systems of record.
Authentication
Access is credential-vaulted and least-privilege. Each integration and each model receives only the scope it needs, tokens are short-lived, and all access is logged to the audit trail.
Resource concepts
- —Entities — unified records in the knowledge graph
- —Decisions — scored, explainable recommendations from the decision engine
- —Workflows — actions executed back into connected systems
- —Audit records — the immutable trail for every decision
Illustrative shape
Concrete endpoints are provisioned per tenant. Conceptually, reads resolve entities and decisions from the graph and writes trigger governed workflows — every call carries tenant scope and is written to the audit trail. The example below is illustrative, not a live endpoint.
- —GET /v1/entities/{id} — resolve a unified entity
- —GET /v1/decisions?scope=… — list scored, explainable decisions
- —POST /v1/workflows/{id}/run — execute a governed action
Getting the full spec
Concrete endpoints, schemas, rate limits, and versioning are provisioned per tenant and shared during onboarding — this page is a conceptual overview, not a live endpoint specification.
This is the public overview. Talk to us for the full API specification for your tenant: concrete endpoints, schemas, auth flows, rate limits, error codes, and versioning.