canonical: https://jentic.com/apis/swaggerhub.dev16/servizi-tessera

# Dev16 Card Services

Card Services - Customer Domain. The API exposes 1 endpoints.

## For AI agents

Programmatically access Card Services resources. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for loyalty card management only.

## Capabilities

- Access Card Services resources via REST API
- Manage loyalty card data programmatically
- Integrate Card Services into automated workflows
- Query and filter Card Services records by parameters
- Monitor Card Services operational status and events

## Use cases

### Loyalty Card Operations

Use the Card Services to perform loyalty card operations programmatically. The API provides 1 endpoints covering core functionality including requesting the point balance of a loyalty card.

Example prompt: Execute a primary operation against the Card Services

### Data Retrieval and Monitoring

Query Card Services resources on a schedule to track changes, generate alerts, or feed downstream dashboards.

Example prompt: Poll the primary Card Services endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Card Services endpoints through Jentic without managing credentials directly.

Example prompt: Search Jentic for 'card services', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/saldopunti` | Request the point balance of a loyalty card |

## Key resources

- **Card Management** — Card management operations

## Why Jentic

- **Setup:** Wiring the Card Services API by hand means resolving its gestionetessera base path, shaping the points-balance call, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Card Services API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API exposes a single read of the points balance, so scoping is about operations: the agent is limited to the saldopunti read you include and nothing else. You choose whether to grant it at all.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check a loyalty card points balance', and Jentic returns the matching Card Services operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Card Services use?

The Card Services uses none authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### What are the rate limits for the Card Services?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I use card services through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use card services'. Jentic returns the matching Card Services operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Card Services have?

The Card Services exposes 1 endpoints covering card management operations.

### Does the Card Services support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Card Services API?

Yes. Because you run Jentic One yourself, your own rules decide which Card Services operations and credentials the agent may use. This API exposes only a single read, the GET on saldopunti that returns a loyalty card's point balance, so you can grant the agent that one point-balance lookup and nothing more, or choose not to expose it at all. The agent cannot call any operation you have not included.