Integration
Connect Checkvist to PokéAPI (GraphQL)
When something happens in Checkvist, your agent does the next thing in PokéAPI (GraphQL). Describe it 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 Checkvist and PokéAPI (GraphQL) 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 Checkvist can start in PokéAPI (GraphQL)
When New List in Checkvist
then Find Pokémon by type in PokéAPI (GraphQL)
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 Checkvist and PokéAPI (GraphQL)
Triggers and actions 2 triggers · 24 actions
- New List
Triggered when a new checklist is created in Checkvist.
- New List Item
Triggered when a new item is added to the chosen Checkvist checklist.
- Close Task
Marks a task in a Checkvist checklist as closed (done) and returns the updated task.
- Create List Item
Adds a new item (task) to a Checkvist checklist and returns the created item.
- Create New List
Creates a new Checkvist checklist and returns it.
- Create Several List Items
Adds several items to a Checkvist checklist at once from a block of text (one item per line) and returns the created items.
- Create Task Note
Adds a note (comment) to a task in a Checkvist checklist and returns the new note.
- Delete Checklist
Deletes a Checkvist checklist and returns the deleted list.
- Delete List Item
Deletes an item (task) from a Checkvist checklist and returns the deleted item.
- Get Checklist
Returns a single Checkvist checklist by its ID, with its name, sharing settings and item counts.
- Get List Item
Returns a single item (task) from a Checkvist checklist, optionally with its notes.
- List Checklists
Returns the Checkvist checklists the connected account can see.
- List List Items
Returns the items (tasks) in a Checkvist checklist.
- List Task Notes
Returns the notes (comments) on a task in a Checkvist checklist.
- Reopen Task
Reopens a closed task in a Checkvist checklist and returns the updated task.
- Update Checklist
Updates a Checkvist checklist's name or sharing setting and returns the updated list.
- Update List Item
Updates an item (task) in a Checkvist checklist and returns the updated item.
- Find Pokémon by type
Return the list of Pokémon that belong to a given elemental type (e.g. fire, water).
- Get ability
Look up details and effect description for a Pokémon ability.
- Get berry
Look up growing details and flavor profile for a berry.
- Get evolution chain
Look up the full evolution chain (pre-evolutions and evolutions) for a given Pokémon species.
- Get item
Look up details for a game item — cost, effect, and category.
- Get move
Look up details for a Pokémon move — power, accuracy, type, damage class, and effect description.
- Get Pokémon
Look up a Pokémon's details (stats, types, abilities, sprites) by name or national dex number via the PokéAPI GraphQL endpoint.
- Get Pokémon species
Look up species-level details for a Pokémon — flavor text, habitat, evolution chain reference, and capture rate.
- List Pokédex entries
List the Pokémon entries contained in a named Pokédex (e.g. national, kanto).
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 Checkvist
Checkvist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Checkvist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Checkvist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Checkvist to Google SheetsGoogle Sheets
Checkvist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Checkvist to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PokéAPI (GraphQL)
Questions
Checkvist and PokéAPI (GraphQL), answered
What can start an automation from Checkvist?
Any of Checkvist's 2 triggers in the catalog, including New List and New List Item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PokéAPI (GraphQL) when something happens in Checkvist?
Any of PokéAPI (GraphQL)'s 9 actions, including Find Pokémon by type, Get ability, Get berry and Get evolution chain. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PokéAPI (GraphQL) to Checkvist?
PokéAPI (GraphQL) has no triggers in the catalog today, so automations start in Checkvist. If you need the other direction, ask: your agent reads PokéAPI (GraphQL)'s API documentation and adds it.
Do I have to build a connector for Checkvist or PokéAPI (GraphQL)?
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.