Skip to main content

​
What are Marketplace Services?

Marketplace services (integration_type = service) are catalog products that expose dedicated HTTP endpoints under your organization context. Unlike enrichments (which attach data to an entity profile), services answer point-in-time queries you call directly from your integration or orchestration layer. Gu1 acts as the tenant-aware proxy: you authenticate with the same API key or session as the rest of the platform; Gu1 resolves organizationId, checks that the product is enabled for your org, applies billing when configured, and returns a normalized JSON envelope.

​
Base path

All service routes share this prefix: 
GET https://api.gu1.ai/api/integration-services/{integrationCode}/...
Replace {integrationCode} with the catalog code (for example ar_gueno_holder_intelligence_service).

​
Authentication

Same as the rest of the Gu1 API: 
Authorization: Bearer YOUR_API_KEY
Session-based dashboard calls are also supported for console tooling; integrators typically use API keys.

​
Activation

The organization must enable the integration in Marketplace (same flow as enrichments and list products). If the integration is not active for the org, paid routes may return billing or configuration errors consistent with other marketplace products.

​
Response envelope

Successful calls return: 
{
  "success": true,
  "data": { }
}
Errors return: 
{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable message"
  }
}
Some endpoints (for example metrics with an incomplete incremental window) may include a partial data object together with success: false and HTTP 422.

​
Billing

  • Free endpoints (for example service health or existence checks) do not charge execution packs or credits.
  • Billable endpoints charge one request unit per successful call when the catalog row has base_price_cents > 0, using the same execution pack / credits model as enrichments.
  • Failed calls due to client validation (400) or CUIT not in corpus (404) are generally not billed; upstream unavailability (503) is not billed.

​
Audit

Every call is logged for the organization (operation key, HTTP status, error code when applicable). CUIT path parameters are never stored in raw form in audit metadata.

​
Rules engine integration

Several services also expose fields under services.{serviceKey}.* in the Rules conditions catalog. When a rule references those paths, Gu1 may hydrate the service during rule execution (separate from direct HTTP calls). See each service overview for rule field mapping.

​
Available services

CBU/CVU Holder Intelligence

Argentina CUIT-linked CBU/CVU totals, contractual windows, and custom incremental metrics (Com. A 8298 BCRA).