API

Integrate analysis, sources, and structured data into your systems.

Apeirum receives documents, events, or questions, queries context and sources, applies workflow rules, and returns JSON, status, callback, report, or reviewable answer.

Conceptual technical flow
JSON
Flow
01POST /documents/analyze
02GET /jobs/{id}
03POST /answers
04callback /system
{
  "input": "Contrato SaaS.pdf",
  "workflow": "contract-analysis",
  "outputs": ["fields", "sources", "status"],
  "review": "required",
  "callback": "/systems/contracts"
}
01

Input

A document, event, or question arrives with origin system, user, and scope.

02

Processing

Apeirum queries context, sources, and rules before structuring the answer.

03

Output

JSON, status, callback, report, or reviewable answer returns to a person or system.

Integration paths

The API role changes with the input and expected output.

Controlled input

Document, question, or event enters with origin, user, purpose, and scope.

Contextual processing

Private AI queries sources, rules, and authorized bases before structuring the answer.

Reviewable output

JSON, status, callback, report, or source-backed answer returns to a person or system.

Conceptual example

Document in, evidence and JSON out.

This block illustrates a scoped commercial integration. It does not expose private RUK endpoints or promise a complete public API without technical scoping.

1
upload
2
job
3
analysis
4
evidence
5
JSON
6
callback
Demo request
POST /api/v1/documents/analyze

{
  "document": "contrato-saas.pdf",
  "workflow": "contract-analysis"
}
Demo response
{
  "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

What can enter the scope

Pricing depends on volume, scope, integrations, operating cost, usage limits, and support level.

Have enough volume or a system to justify integration?

Describe which documents, systems, data, and outputs must enter the flow: answer, report, structured field, JSON, or integration.