Take the context of your business to the products and agents you build.

SOCEO APIS

SOCEO APIs connect data, sources, permissions and actions into an operational layer that other applications rely on.

View documentation Understand the platform

API Documentation

SOURCES AND SYSTEMS Customer relationships Documents Operations OPERATIONAL LAYER Context Permissions Provenance Declared gaps SOCEO SOCEO API GOVERNED BOUNDARY WHAT YOU BUILD Agents Products Workflows Provenance preserved Identity respected Results returned to context EXPLORE THE API ↓

BUILDING ON THE CONTEXT OF THE BUSINESS

A common layer between what business knows and what you want to build.

SOCEO APIs begin in the operational context: the right data, within the right scope, with a clear path back to the source.

01 CONTEXTUAL ANSWER Orders Campaigns ANSWER There is a relationship between falling conversion rates and outdated ad creatives. 2 sources 1 gap Context

See related information, preserving source, update and permissions.

02 WORK SCOPE AI MISSION CONTEXT Objective 6 sources Permissions No access outside the scope Agents

Deliver agents a structured view of the operation without repeating the entire business in each prompt.

03 GOVERNED EXECUTION 01 PROPOSAL Campaign review prepared 02 CHECKPOINT Human approval pending 03 WORK Owner + controlled deadline Workflows and actions

Turn responses into controlled work, with approval, owner, deadline and history when necessary.

EXPERIENCE FOR DEVELOPERS

An interface made for the builder.

See context, preserve sources and permissions, and turn responses into controlled actions with a consistent interface.

01 Query context 02 Create an action 03 Track a result INTEGRATION EXAMPLE Copy const leitura = await soceo.contexto.consultar({ identidade: "agente-campanhas", pergunta: "Which operational change needs attention?", incluir: ["fontes", "permissoes", "lacunas"] });

return { resposta: leitura.contexto, fontes: leitura.fontes, lacunas: leitura.lacunas }; Answer with sources, permissions and gaps OPERATIONAL API

DOCUMENTATION

Consult contracts, references and examples of integration.

See OpenAPI documentation + examples

API CAPABILITIES

An API to consult, decide and act with real context.

See what the business knows, preserve the origin of each response and transform context into controlled work.

SOCEO API

ALL OPERATIONAL SYSTEMS

01 INPUT Endpoints POST /v1/context/query Query context

Ask about entities, relationships and business events.

GET /v1/sources/{id} Trace sources

Return to the source used in any response, decision or action.

GET /v1/events Track events

Receive relevant changes with preserved history and context.

POST /v1/actions Create actions

Convert an answer into work with owner, deadline and approval.

CORE SOCEO Context OPERATIONAL API Context Identity Permissions Gaps RESPONSE Structured response 200 OK { "contexto": { ... }, "fontes": [ ... ], "lacunas": [ ... ], "proxima_acao": { ... } } Products Agents Workflows OpenAPI

Contracts, references and examples of integration.

Authorisation

Scope applied to the identity of each person or agent.

Observability

Complete trail between query, source, action and result.

SECURITY AND AUTHORITY

Useful context without taking the business out of command.

The API is a boundary of the platform. It doesn't replace the rules that define who can see, interpret or do something.

CENTRAL RULE SOCEO backend Operational authority Identity received Rule applied Authorized response 01 The backend is the authority

The interface requests. Business rules decide what can be consulted or executed.

02 Person and agent on the same perimeter

The agent's identity respects permissions linked to the same data.

03 The result returns to the context

Answer, decision and action return to context to reflect what really happened.

04 Sources follow important responses

Origin remains navigable for review, explanation and contestation when necessary.

05 A gap does not become certainty

Absence, delay, or data conflict should appear as a limit, never as an invented conclusion.

06 Sensitive actions may require a human checkpoint

Approval, owner and scope may be required before an action ceases to be proposed and becomes work.

request → rule applied → response or action authorized

FREQUENT QUESTIONS

Everything you need to get started. Understand the platform 01 How do I start using the SOCEO APIs?

Access the documentation, create your key and choose the workspace whose context your application will consult.

02 What can I build? 03 How does SOCEO protect permissions and sources? 04 Where do I find the documentation? 05 Can I connect agents to APIs?

SOCEO APIS

Build on a business AI can understand.

Consult the documentation, connect your application and build with the real business context.

See documentation Talk to team Documentation, references and examples of integration