Overview
Integration code: ar_gueno_holder_intelligence_service
This Gu1 marketplace service queries the internal holder corpus (Argentina CUIT/CUIL, 11 digits) for:
- Whether a tax ID appears in the processed corpus
- Current CBU and CVU account totals linked to the holder
- Contractual lookback windows (
w_1d … w_180d) with deltas and variance
- Custom incremental metrics over a calendar lookback (1–180 days) including % change and acceleration
Gu1 proxies the corpus on your behalf. Integrators do not call holder-score directly.
Regulatory context: aligned with BCRA Com. «A» 8298 (holder totalizers / AML-CFT use cases). Product activation may depend on org eligibility.
Base path
https://api.gu1.ai/api/integration-services/ar_gueno_holder_intelligence_service
Path parameter: CUIT
All /cuits/:cuit/... routes require exactly 11 digits, no dashes.
| Valid | Invalid |
|---|
20384648798 | 20-38464879-8 |
| 2038464879 |
Endpoints
| Endpoint | Billing | Description |
|---|
| Health | No | Service and corpus freshness |
| Exists | No | Membership check (found true/false) |
| Accounts count | Per request when priced | CBU/CVU totals + holder metadata |
| Windows | Per request when priced | Contractual windows w_1d–w_180d |
| Metrics | Per request when priced | Custom lookback metrics |
Common error codes
| Code | HTTP | Meaning |
|---|
CUIT_NOT_FOUND | 404 | CUIT absent from processed corpus (paid routes) |
SERVICE_UNAVAILABLE | 503 | Holder backend down or not configured |
SERVICE_INTEGRATION_NOT_ACTIVE | 403/404 | Product not enabled for org |
INSUFFICIENT_BALANCE | 402 | Credits or execution pack exhausted |
INVALID_WINDOW | 400 | Invalid window query (windows route) |
INVALID_LOOKBACK | 400 | Invalid lookback query (metrics route) |
INVALID_DATE | 400 | Invalid date query (YYYY-MM-DD) |
INCOMPLETE_WINDOW | 422 | Incremental window incomplete for requested lookback |
NO_INCREMENTAL_STATE | 422 | No incremental state for this CUIT |
INTERNAL_ERROR | 500 | Unexpected server error |
Rules engine
Rule conditions use paths such as:
services.holder_intelligence.cbu_quantityoriginEntityData.services.holder_intelligence.metrics.cbu_acceleration
See Rules conditions — services for the full field list.
For transaction rules, custom metrics default to a reference calendar date from transactedAt (Argentina timezone). Configure holderIntelligenceLookbackDays (1–180) on each metrics condition.
When a rule references holder fields, Gu1 hydrates the service during execution (opt-in fetch). Direct HTTP calls and rule hydration share the same upstream semantics but are billed independently when priced.
