Judicial operations + production-ready APIs

Run OJV tracking, internal matters, and automation from one operational front door.

Nexulex connects judicial monitoring, internal matter management, organizational governance, and developer tooling for teams that need integration without losing traceability.

Built for modern legal operations: public visibility, clear internal workflows, and a technical surface that can be trusted from day one.

Explore API docs View OJV status

OJV monitoring with public status and operational context.

Internal matters that can connect multiple OJV cases in one matter.

Bilingual API docs and organization-scoped developer keys.

SaaS

Nexulex

OJV tracking, internal matters, billing, governance, and builder tooling inside one coherent product story.

Operational coverage

The foundation for teams that combine legal operations, governance, and product.

OJV

monitoring and public health

Public status, recent history, and clear signals before escalating a judicial connectivity incident.

360

connected internal matters

Internal matters with owners, metadata, cost, time, and multiple linked OJV records.

API

reliable technical surface

Bilingual documentation, audience-aware routes, and secure developer keys for organizations.

Ops

governance and traceability

Roles, organizational scope, and operational visibility for day-to-day work and auditability.

Capabilities

A full legal operations stack, not a patchwork of disconnected tools.

Tracking

OJV cases with actionable context

Track cases, review activity, control delays, and confirm ecosystem health without leaving the workspace.

Matters

Connected internal matters

Relate one internal matter to zero, one, or many OJV cases so the business narrative stays in one place.

Governance

Clear organization, teams, and permissions

Combine organization scope, assignments, and internal configuration to operate with less ambiguity.

Builders

APIs ready to validate

Explore public and protected endpoints, understand requirements, and validate integrations before production.

Status

Public confidence around platform health

The public experience makes it obvious when OJV or PJUD are having issues so support and operations start with context.

Scale

One front door for ops and product

The same platform serves operational teams, organizational leadership, and technical builders integrating legal data.

Product view

A workspace that connects cases, teams, and system signals.

Every module follows the same operational story: case origin, internal relationships, system state, and the next action.

Judicial operations

Day-to-day tracking for teams living inside judicial workflows and needing to spot changes quickly.

OJV case tracking and daily activity

Daily case and room schedules

Delay radar and operational signals

Internal matters and work

Unify ownership, operational work, and the internal story around your matter model.

Internal matters with multiple linked cases

Work queue, calendar, and team ownership

Documents, time, cost, and matter notes

Access and knowledge

Give teams clear access scope plus knowledge tools that reduce friction across the workspace.

OJV access control and organization scope

RUT lookup and case-law workspaces

Organization settings and internal metadata

Billing, builders, and admin

Bring shared operations, technical integration, and privileged governance into the same product stack.

Billing, organization operations, and support

API docs and organization-scoped keys

Admin console and governance surfaces

Commercial estimator

Project your monthly bill with Chile-specific rules kept explicit.

This estimator uses Nexulex public commercial defaults. Your final invoice depends on your real organization configuration and the invoiced period.

Plan

Starter

No fixed monthly base

No commercial cap

Plan

Active connected causes per month

Only OJV or other scraper-backed causes connected to your organization count in this estimate.

API requests per month

Included allowance always scales from billable connected causes, and it is capped by the plan limit when one exists.

Starter

Estimated monthly bill

CLP 27,500

Starter has no fixed monthly base. It applies marginal bands to active connected causes and only adds API overage once the included allowance is exhausted.

Monthly plan base

No fixed monthly base

Connected-cause charge

CLP 27,500

Billable connected causes

Included API allowance

15,000

Requests above allowance

Estimated API overage

No API overage in this scenario.

Public estimator only. The final invoice uses the real organization plan, caps, included allowance, and measured usage.

Technical trust

Public API docs, secure keys, and operational visibility from the start.

Use the public surface to explore routes, validate integrations, and review system health before moving critical work.

Bilingual API docs

Explore endpoints, examples, and requirements from a public explorer built for fast validation.

Organization-scoped keys

Organizations manage their own keys and visibility without exposing internal-only or superadmin routes.

Public OJV health

Confirm OJV and PJUD availability before escalating connectivity or integration incidents.

Public API docs, secure keys, and operational visibility from the start.

Use the public surface to explore routes, validate integrations, and review system health before moving critical work.

Open API docs Sign up

Nexulex

Put your operational and technical teams on the same page.

Create an account, explore the product, and connect Nexulex to your internal workflows without losing governance, support, or visibility.