Fidel API

@fidel-api show me the details for brand ID brd_a1b2c3d4 including all active programs and their current status

Retrieved brand 'Acme Retail Group' (brd_a1b2c3d4). This brand has 3 active programs: 'Summer Rewards' (online, 2,847 enrolled cards), 'In-Store Cashback' (offline, 1,203 enrolled cards), and 'VIP Tier' (online, 89 enrolled cards). The brand was created on 2023-06-15 and last updated on 2024-01-10. All programs are currently active with no pending configuration changes. This is an illustrative example based on typical API response structure.

Requires a valid brand ID from your Fidel API account. The Get Brand tool returns metadata only—it won't include transaction history or cardholder PII. Useful for auditing program configurations before making changes or debugging webhook delivery issues tied to specific brands.

@fidel-api create a new program called 'Holiday Bonus 2024' for offline purchases with metadata tracking campaign source as 'email-december'

Created program 'Holiday Bonus 2024' with ID prg_x9y8z7w6. Program type set to offline (in-store transactions). Metadata field 'campaign_source' recorded as 'email-december' for attribution tracking. The program is now active and ready to accept card enrollments. You'll need to configure offers separately using the program ID. This is an illustrative example of a successful program creation response.

Program creation is immediate but requires a parent brand ID (you may need to create a brand first). The 'offline' vs 'online' distinction affects which transaction types trigger webhooks. Remember to set up program webhooks separately if you need real-time transaction notifications—program creation doesn't auto-configure event listeners.

@fidel-api list all active offers across my programs and draft a summary comparing their performance metrics and expiration dates

I don't have a direct 'list all offers' tool in this MCP, but I can retrieve individual offers by ID using Get Offer. To generate a performance comparison, you'd need to provide specific offer IDs (e.g., from a previous export or dashboard). Once I have those IDs, I can fetch each offer's details—including redemption rules, date ranges, and qualifying merchant categories—then synthesize a comparison table highlighting which offers expire soonest and their configured reward rates. This workflow requires you to supply the offer IDs first.

This example reveals a limitation: the Fidel API MCP provides granular tools (get/create/delete individual resources) but lacks bulk-list endpoints for offers or transactions. For cross-program analysis, you'll need to maintain offer IDs externally or query them via the Fidel dashboard first. The MCP excels at targeted operations once you know the resource ID.

When Fidel API handles card-linked offers at launch scale

A 6-person team launching a card-linked loyalty program for a regional coffee chain with 40 locations needs to onboard brands, create programs per location cluster, and register webhooks for real-time transaction events. Fidel API's 18 tools cover the full lifecycle: Create Brand registers the chain, Create Program sets up location-specific campaigns, and Create Program Webhook pipes transaction data into your CRM. The API key auth keeps setup simple—no OAuth dance when you're racing to a beta launch. This MCP wins if you're building the loyalty stack from scratch and need programmatic control over brands, programs, and offer lifecycle. If you're only reading transaction data or integrating an existing loyalty platform, a simpler webhook-only integration beats spinning up 18 tools. Use this when you're the engineering team behind the loyalty product, not just consuming it.

Why Fidel API fits real-time fraud detection workflows

A 3-person fintech startup monitoring card transactions for spend-pattern anomalies needs webhook endpoints that fire the instant a linked card swipes. Fidel API's Create Program Webhook and Delete Webhook tools let you register listeners for transaction.auth events, then tear them down when testing rules or rotating endpoints. The Get Offer tool pulls current promotion details to cross-check whether a flagged transaction matches an active campaign. This MCP is the right call if your compliance logic runs in-house and you need sub-second event delivery with full CRUD control over webhook configs. The 18-tool surface area is overkill if you only consume a static feed—Fidel's dashboard can register webhooks without code. Choose this integration when your fraud model needs to dynamically subscribe to event streams as you onboard new merchant programs or test detection rules in staging.

When Fidel API supports campaign analytics at agency scale

A 5-person marketing ops team running card-linked offers for 12 QSR clients needs to pull offer metadata, compare redemption rates, and archive expired campaigns each quarter. Fidel API's Get Offer retrieves current terms and performance snapshots, while Delete Offer cleans up ended promotions so the client dashboard stays current. The Get Brand tool maps offers back to parent brands when building cross-client reports. This MCP works if you're the agency managing offers programmatically across multiple brands and need read-write access beyond what a BI dashboard exports. The trade-off: if your reporting is monthly and read-only, Fidel's native analytics or a scheduled CSV export is faster than maintaining 18 MCP tools. Use this when you're automating offer lifecycle management—creating, auditing, and sunsetting campaigns—not just pulling static reports.