Digitalwallet Cards TRYB Loyalty API
40
AI ReadinessFoundational (D-)40/100
Agent-ready OpenAPI document · curated by JenticCRMCustomer SuccessapiKey43 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Run a digital loyalty program: create loyalty cards, add or subtract points, stamps, and rewards, manage customers and promotions, set membership tiers, and send push or SMS.
Use for: Create a loyalty card for a customer, Add points to a customer's loyalty card, Add a stamp to a card after a visit, Redeem a coupon on a card
Not supported: Does not handle payment processing, inventory, or point-of-sale hardware. Use for managing loyalty cards, customers, and rewards only.
Jentic publishes the only available OpenAPI specification for TRYB Loyalty API, keeping it validated and agent-ready. The TRYB Loyalty API runs a digital loyalty program: it creates and manages loyalty cards for customers and adjusts points, stamps, visits, purchases, and rewards on each card. It manages customer records and promotions, sets membership tiers and expiration dates, redeems coupons, sends push notifications and SMS, and reports revenue statistics.
Install Jentic One Beta
Connect the TRYB Loyalty API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TRYB Loyalty API, 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%2Fdigitalwallet.cards%2Fdigitalwallet" | 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%2Fdigitalwallet.cards%2Fdigitalwallet" | 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 TRYB Loyalty API.
Create and manage loyalty cards for customers
Add or subtract points, stamps, visits, purchases, and rewards on a card
Redeem coupons and record reward receipts on a card
Set a card's membership tier, expiration date, and reward tiers
Manage customer records and create promotions
Send push notifications and SMS messages to customers
Retrieve revenue statistics and operation history
Use Cases
Patterns agents use TRYB Loyalty API for, with concrete tasks.
★ Agent-Run Loyalty Point Updates
An AI agent handling point-of-sale events can create a customer's loyalty card, add points or stamps after a purchase, and redeem coupons through the TRYB Loyalty API. Because each action maps to a card operation, the agent keeps balances current without a staff member touching the loyalty dashboard.
Create a loyalty card for a customer, then add points to that card after a purchase
Promotions and Customer Messaging
Marketing workflows can create promotions and reach cardholders with push notifications and SMS using the TRYB Loyalty API. The promotion and messaging operations let a campaign target customers who hold a loyalty card.
Create a promotion, then send a push notification announcing it to customers
Membership Tiers and Revenue Reporting
Program managers can set membership tiers and expiration dates on cards and pull revenue statistics from the TRYB Loyalty API. This supports tiered loyalty programs where benefits and reporting depend on a customer's current tier.
Set a card's membership tier, then retrieve the program's revenue statistics
Key Endpoints
43 endpoints — jentic publishes the only available openapi specification for tryb loyalty api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/api/v2/cards
Create card for customer
GET
/api/v2/cards/{id}
Get card
POST
/api/v2/cards/{id}/add-point
Add point to card
POST
/api/v2/cards/{id}/add-stamp
Add stamp to card
POST
/api/v2/cards/{id}/redeem-coupon
Redeem coupon
POST
/api/v2/customers
Create customer
POST
/api/v2/promotions
Create promotion
POST
/api/v2/pushes
Send push
POST
/api/v2/cards
Create card for customer
GET
/api/v2/cards/{id}
Get card
POST
/api/v2/cards/{id}/add-point
Add point to card
POST
/api/v2/cards/{id}/add-stamp
Add stamp to card
POST
/api/v2/cards/{id}/redeem-coupon
Redeem coupon
POST
/api/v2/customers
Create customer
POST
/api/v2/promotions
Create promotion
POST
/api/v2/pushes
Send push
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
TRYB Loyalty API
- Foundational (D-)40/100
58
Foundational Compliance57
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
58
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
90%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
95%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
15%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the TRYB Loyalty API by hand means managing its X-API-Key header and keeping track of dozens of card operations for points, stamps, visits, rewards, and tiers. Through Jentic you install once, import the TRYB Loyalty API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The TRYB Loyalty API puts the card, customer, and promotion ids in the URL path, such as /api/v2/cards/{id}, so a rule can pin your agent to the operations and resources it needs. You choose which operations it may call, so it can add points and redeem coupons without being able to delete cards or customers unless you add those operations.
Credential isolation
Your TRYB API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add points to a loyalty card' or 'create a promotion', and Jentic returns the matching TRYB operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using TRYB Loyalty API through Jentic.
Why is there no official OpenAPI spec for TRYB Loyalty API?
TRYB does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the TRYB Loyalty API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the TRYB Loyalty API use?
The TRYB Loyalty API authenticates with an API key sent in the `X-API-Key` header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I add points to a loyalty card with the TRYB Loyalty API?
Yes. The TRYB Loyalty API has operations to add and subtract points, stamps, visits, purchases, and rewards on a card by its id, plus redeem coupons and set membership tiers. You can create the card first if the customer does not have one yet.
What are the rate limits for the TRYB Loyalty API?
The OpenAPI spec does not specify rate limits for the TRYB Loyalty API. Check the provider's documentation at https://digitalwallet.cards for the current limits that apply to your API key.
Can I limit what my agent is allowed to do with the TRYB Loyalty API?
Yes. Card, customer, and promotion ids travel in the URL path, so a rule can scope your agent to the operations and resources it needs. Write a rule that allows only point and stamp updates and coupon redemption, so the agent can run everyday loyalty actions without being able to delete cards or customers, and every call it makes is logged.
How do I update a loyalty card with the TRYB Loyalty API through Jentic?
Search Jentic for 'add points to a loyalty card' and it returns the matching TRYB operation with its input schema. Import the TRYB Loyalty API from the Jentic API Directory, store your API key once, and your agent can create cards, adjust points and stamps, and redeem coupons without hand-wiring the key on each request.
Is there a TRYB Loyalty API MCP server?
You don't need an MCP server to give your agent the TRYB Loyalty API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the card, customer, and promotion operations. Nothing extra loads into the agent's context until an operation is actually used.
GET STARTED