Dev16 Card Services
Browse all Swaggerhub Dev16 APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access Card Services resources. Covers 1 operations.
Use for: I need to integrate with Card Services, Find available loyalty card operations, Get the current status of Card Services resources, List all records from Card Services
Not supported: Does not handle payments, communications, or crm - use for loyalty card management only.
Card Services - Customer Domain. The API exposes 1 endpoints.
Install Jentic One Beta
Connect the Card Services to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Card Services, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.dev16%2Fservizi-tessera" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.dev16%2Fservizi-tessera" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Card Services API.
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
Patterns agents use Card Services API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'card services', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — card services - customer domain.
METHOD
PATH
DESCRIPTION
GET
/saldopunti
Request the point balance of a loyalty card
GET
/saldopunti
Request the point balance of a loyalty card
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Card Services API through Jentic.
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.
GET STARTED