Integration
Connect Fidel Api to Stedi
When New transaction fires in Fidel Api, your agent runs Add event destination in Stedi. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Fidel Api and Stedi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Fidel Api can start in Stedi
When New transaction in Fidel Api
then Add event destination in Stedi
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Fidel Api and Stedi
Triggers and actions 1 trigger · 20 actions
- New transaction
Fires on a new card transaction.
- Add brand
Creates a new brand in your Fidel API account.
- Add offer
Creates a new offer for a brand in your Fidel API account.
- Add program
Creates a new loyalty program in your Fidel account.
- Get brand
Returns the details of a single brand by its ID.
- Get card
Returns a single card by its ID, including its scheme, last digits, expiry and program.
- Get transaction
Returns a single card transaction by its ID, including amount, currency, card, location and brand details.
- List brands
Returns the brands in your Fidel account, optionally filtered by name.
- List locations
Returns the locations registered under a Fidel program, optionally filtered by postcode or sync status.
- List programs
Returns the loyalty programs on your Fidel account.
- List transactions
Returns the transactions recorded on a Fidel program, optionally filtered by date range and sorted by transaction time.
- Update brand
Updates a brand's website, logo or metadata.
- Add event destination
Create a new event destination for receiving Stedi webhook events.
- Check eligibility
Runs a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response.
- Delete event destination
Permanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED.
- Find payers by criteria
Searches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance.
- Get event destination
Retrieve an event destination by id.
- Get payer
Retrieve a single payer record by id.
- List event destinations
Lists the event destinations configured in your Stedi account, optionally filtered by status or event type.
- List payers
Lists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements.
- Update event destination
Updates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Fidel Api
Fidel Api to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Fidel Api to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Fidel Api to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Fidel Api to Google SheetsGoogle Sheets
Fidel Api to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Fidel Api to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Stedi
Questions
Fidel Api and Stedi, answered
What can start an automation from Fidel Api?
Any of Fidel Api's 1 trigger in the catalog, including New transaction. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Stedi when something happens in Fidel Api?
Any of Stedi's 9 actions, including Update event destination, Add event destination, Check eligibility and Find payers by criteria. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Stedi to Fidel Api?
Stedi has no triggers in the catalog today, so automations start in Fidel Api. If you need the other direction, ask: your agent reads Stedi's API documentation and adds it.
Do I have to build a connector for Fidel Api or Stedi?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Fidel Api and Stedi without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.