Billing based on connected causes and real technical consumption.
Nexulex charges for what actually matters: OJV or other scraper-backed causes connected to the organization, plus API overage only when the monthly included allowance runs out.
Starter
UNITARYNo fixed monthly base
No commercial cap
UNITARY mode for teams that want to scale by marginal bands and pay only for active connected causes.
Advanced
BUNDLE119,900 CLP + IVA / month
Up to 300 connected causes
BUNDLE mode for organizations that want one flat monthly amount up to a configured connected-cause maximum.
Enterprise
FIX299,900 CLP + IVA / month
Up to 1,000 connected causes
FIX mode for negotiated lump sums with a configured maximum of connected causes and stronger governance needs.
Starter
UNITARYNo fixed monthly base
No commercial cap
UNITARY mode for teams that want to scale by marginal bands and pay only for active connected causes.
- Marginal billing per active connected cause.
- Included monthly API allowance for every billable connected cause.
- Best fit for smaller firms or teams still ramping up.
Advanced
BUNDLE119,900 CLP + IVA / month
Up to 300 connected causes
BUNDLE mode for organizations that want one flat monthly amount up to a configured connected-cause maximum.
- Flat monthly amount for the configured bundle.
- Hard cap on connected causes included in the bundle.
- Best fit for controlled medium-volume operations.
Enterprise
FIX299,900 CLP + IVA / month
Up to 1,000 connected causes
FIX mode for negotiated lump sums with a configured maximum of connected causes and stronger governance needs.
- Negotiated flat monthly lump sum.
- Configured maximum of connected causes included in the contract.
- Built for larger teams, integrations, and privileged admin coverage.
Starter uses marginal connected-cause pricing.
1-50 connected causes: 400 CLP VAT included per cause each month.
51-250 connected causes: 300 CLP VAT included per cause each month.
251+ connected causes: 200 CLP VAT included per cause each month.
Included API capacity grows with billable connected causes.
Every billable connected cause unlocks 200 requests per month. Metered API only starts after that monthly included capacity is exhausted.
50 billable connected causes => 10,000 included requests per month.
Bundle and lump-sum contracts measure allowance on active connected causes, up to the configured cap for that plan.
If usage goes beyond the monthly allowance, only that excess enters the API meter.
API overage: 1,500 CLP per 1,000 requests.
Three billing shapes, one source of truth.
| Starter | Advanced | Enterprise | |
|---|---|---|---|
| Billable unit | Connected cause | Connected cause | Connected cause |
| Billing shape | Marginal bands | Flat bundle | Flat lump sum |
| Cause cap | No plan cap | Configured cap | Configured cap |
| Included API allowance | 200 per billable cause | 200 per billable cause up to the cap | 200 per billable cause up to the cap |
| API overage | 1,500 / 1,000 requests | 1,500 / 1,000 requests | 1,500 / 1,000 requests |
Pricing and contracts explained with visible rules.
Billing is framed in CLP, with IVA (VAT) and organization-level financial profile coverage.
Bundle and lump-sum modes control how many connected causes fit inside the monthly amount.
Internal matters alone are not billable; the billable unit is the scraper-backed connected cause.
API usage is measured per organization and compared against the included monthly allowance.
Common questions before turning billing on.
Only connected causes from OJV or other supported scrapers, plus API overage when the organization exceeds its included monthly allowance.
The platform keeps a hard cap. A new connected cause does not enter tracking until the configuration or plan changes.
No. Internal matters coordinate work, but they are not the billable unit by themselves.
Activate a billing model your team can actually explain.
Review UNITARY, BUNDLE, and FIX with clear rules for Chile, then start with a pricing model that matches connected-cause reality.