Input
A document, event, or question arrives with origin system, user, and scope.
Apeirum receives documents, events, or questions, queries context and sources, applies workflow rules, and returns JSON, status, callback, report, or reviewable answer.
{
"input": "Contrato SaaS.pdf",
"workflow": "contract-analysis",
"outputs": ["fields", "sources", "status"],
"review": "required",
"callback": "/systems/contracts"
}A document, event, or question arrives with origin system, user, and scope.
Apeirum queries context, sources, and rules before structuring the answer.
JSON, status, callback, report, or reviewable answer returns to a person or system.
Integration paths
Document, question, or event enters with origin, user, purpose, and scope.
Private AI queries sources, rules, and authorized bases before structuring the answer.
JSON, status, callback, report, or source-backed answer returns to a person or system.
This block illustrates a scoped commercial integration. It does not expose private RUK endpoints or promise a complete public API without technical scoping.
POST /api/v1/documents/analyze
{
"document": "contrato-saas.pdf",
"workflow": "contract-analysis"
}{
"status": "completed",
"document_type": "contract",
"fields": {
"monthly_value": "R$ 18.900,00",
"implementation_fee": "R$ 42.000,00"
},
"sources": [
{
"page": 2,
"section": "Valores e reajuste"
}
]
}Business integration
Pricing depends on volume, scope, integrations, operating cost, usage limits, and support level.
AI answers inside existing systems, internal portals, CRMs, ERPs, or SaaS products.
Classification, summaries, comparison, field extraction, and document review with context.
AI-supported flows for triage, reporting, classification, and review without promising autonomous automation outside scope.
Interfaces and integrations to support legal, finance, compliance, support, and operations teams.
Describe which documents, systems, data, and outputs must enter the flow: answer, report, structured field, JSON, or integration.