Integration

Connect Swapcard Organizer to F1 API

When New Exhibitor fires in Swapcard Organizer, your agent runs Find drivers by name in F1 API. Describe the whole flow and it is built, tested on every scenario and kept running.

Swapcard Organizer4 triggers Swapcard Organizer14 actions F1 API12 actions

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 Swapcard Organizer and F1 API to do together?

Ask the assistant

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide

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

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

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

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

Example flows

What Swapcard Organizer can start in F1 API

When New Exhibitor in Swapcard Organizerthen Find drivers by name in F1 API
When New Person in Swapcard Organizerthen Find teams by name in F1 API

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 Swapcard Organizer and F1 API

Triggers and actions 4 triggers · 26 actions

Trigger
New Exhibitor
Triggers when a new exhibitor is created inside the event.
Trigger
New Person
Triggers when a new person is created inside the event.
Trigger
Updated Exhibitor
Triggers when a exhibitor is updated inside the event.
Trigger
Updated Person
Triggers when a person is updated inside the event.
Action
Add or Remove a Badge to a Person in an Event
Add or remove a badge to a peson in an event.
Action
Add or Remove a Person as Member of the Exhihitors
Add or remove a person as member of the exhibitors.
Action
Create Exhibitor
Create a new exhibitor on the event.
Action
Create Person
Creates a new event person.
Action
Find a Person
Find for a person by a specific field.
Action
Get event
Get one event by id.
Action
Get Event Person
Returns one event person by id, including groups, badges and session attendance (event-admin GraphQL eventPerson).
Action
Get Event Person Badges
Returns the badges (barcodes: type and value) assigned to one person in an event, via the eventPerson GraphQL query with an eventPeopleIds filter selecting badges { ... on BadgeBarcode }.
Action
List events
List events in the organizer account.
Action
List exhibitors
List exhibitors of an event.
Action
Search Planning by Id
Find an planning by id.
Action
Update Event Person Groups
Update an event person groups.
Action
Update exhibitor
Update an exhibitor in an event.
Action
Update Person
Update a event person.
Action
Find drivers by name
Searches Formula 1 drivers by first name or surname and returns the matching drivers.
Action
Find teams by name
Finds Formula 1 teams whose name matches the search text.
Action
Get driver
Returns the details of one Formula 1 driver — name, nationality, birthday, racing number and short name.
Action
Get driver standings
Returns the drivers' championship standings for a season, with each driver's position, points, wins and team.
Action
Get team
Returns the details of a Formula 1 team, including its nationality, first appearance and championship counts.
Action
List circuits
Returns all Formula 1 circuits, both active and historic, with location, length and lap record details.
Action
List drivers
Returns all Formula 1 drivers in the database, both active and retired.
Action
List drivers by season
Returns every Formula 1 driver who took part in the given season, with their team.
Action
List races by season
Returns the races of a Formula 1 season, with schedule, circuit, winner and winning team for each race.
Action
List seasons
Returns the Formula 1 World Championship seasons, with each season's year, name and Wikipedia link.
Action
List teams
Returns all Formula 1 teams, active and historic, with their nationality and championship counts.
Action
List teams by season
Returns the Formula 1 teams that competed in a given season.

Each app on its own

Reviews

What our customers say

More into F1 API

Questions

Swapcard Organizer and F1 API, answered

What can start an automation from Swapcard Organizer?

Any of Swapcard Organizer's 4 triggers in the catalog, including New Exhibitor, New Person, Updated Exhibitor and Updated Person. Describe the moment in plain language and your agent picks the right one.

What can your agent do in F1 API when something happens in Swapcard Organizer?

Any of F1 API's 12 actions, including Find drivers by name, Find teams by name, Get driver and Get driver standings. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from F1 API to Swapcard Organizer?

F1 API has no triggers in the catalog today, so automations start in Swapcard Organizer. If you need the other direction, ask: your agent reads F1 API's API documentation and adds it.

Do I have to build a connector for Swapcard Organizer or F1 API?

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 Swapcard Organizer and F1 API 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.

Connect Swapcard Organizer to F1 API

What do you want Swapcard Organizer and F1 API to do together?

What Swapcard Organizer can start in F1 API

Triggers and actions 4 triggers · 26 actions

Each app on its own

What our customers say

More from Swapcard Organizer

More into F1 API

Swapcard Organizer and F1 API, answered

What can start an automation from Swapcard Organizer?

What can your agent do in F1 API when something happens in Swapcard Organizer?

Can it also run from F1 API to Swapcard Organizer?

Do I have to build a connector for Swapcard Organizer or F1 API?

Can my AI client use Swapcard Organizer and F1 API without building an automation?

What happens when something fails?

Is there a free plan?