Integration
Connect Bart to Stedi
When New service advisory fires in Bart, 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 Bart and Stedi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Bart can start in Stedi
When New service advisory in Bart
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 Bart and Stedi
Triggers and actions 1 trigger · 17 actions
- New service advisory
Triggers when BART posts a new service advisory (delay, emergency or information notice).
- Find trips by origin and destination
Finds BART trips departing from an origin station to a destination station around a given time, with fares and legs for each trip.
- Get route
Returns details for a BART route: its name, colour, origin and destination, and the ordered list of stations it serves.
- Get station
Returns detailed information about a BART station, including its address, location, routes, platforms and nearby attractions.
- Get station schedule
Returns the full day's scheduled train departures from a BART station, with line, destination, time and platform for each.
- List real-time departures
Returns the current estimated departure times for trains leaving a BART station, grouped by destination.
- List routes
Returns the list of BART routes (lines) in service for the current or a chosen schedule date.
- List service advisories
Returns BART's current service advisories (delays, emergencies and general information).
- List stations
Returns every BART station with its full name, abbreviation, coordinates and address.
- 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 Bart
Bart to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bart to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bart to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bart to Google SheetsGoogle Sheets
Bart to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bart to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Stedi
Questions
Bart and Stedi, answered
What can start an automation from Bart?
Any of Bart's 1 trigger in the catalog, including New service advisory. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Stedi when something happens in Bart?
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 Bart?
Stedi has no triggers in the catalog today, so automations start in Bart. 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 Bart 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.
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.