Integration
Connect LiquiLens and TicketCo
When New flagged institution fires in LiquiLens, your agent runs Find Customers in TicketCo, or New Event in TicketCo to Check institution risk in LiquiLens. 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 LiquiLens and TicketCo 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 LiquiLens and TicketCo can do together
From LiquiLens to TicketCo
When New flagged institution in LiquiLens
then Find Customers in TicketCo
When New flagged institution in LiquiLens
then Get Event in TicketCo
From TicketCo to LiquiLens
When New Event in TicketCo
then Check institution risk in LiquiLens
When New Transaction in TicketCo
then Find institutions in LiquiLens
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 LiquiLens and TicketCo
Triggers and actions 3 triggers · 10 actions
Trigger
New flagged institutionFires when a new institution is added to the failure-risk board.
Action
Check institution riskRun a risk check against an institution and return its current failure-risk assessment.
Action
Find institutionsSearch the public RBI institution universe by name to find matching institutions.
Action
Get institution risk profileRetrieve one covered institution's full public risk dossier, including underlying filings and regulatory actions cited as evidence.
Action
List flagged institutionsRead the current institution-risk board of banks and lenders flagged for failure risk.
Trigger
New EventTriggers when a new event appears in your TicketCo account.
Trigger
New TransactionTriggers when a new ticket transaction is recorded in TicketCo.
Action
Find CustomersReturns TicketCo customers, optionally filtered by email, ID or last update time.
Action
Get EventReturns one TicketCo event by its ID, with its title, location, dates, prices and ticket types.
Action
Get Event StatusReturns the current status of one TicketCo event.
Action
Get MembershipReturns one TicketCo membership with its members.
Action
List EventsReturns the organizer's active and ended TicketCo events, filterable by title, type, location, status and start date.
Action
List TransactionsReturns TicketCo ticket transactions, filterable by event, customer, buyer email, invoice and reference number.
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 LiquiLens
LiquiLens to VercelVercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.
LiquiLens to Open DiseaseOpen Disease Data (disease.sh) is a public epidemiology data service that aggregates COVID-19, influenza and...
LiquiLens to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LiquiLens to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LiquiLens to MailchimpMailchimp marketing automation and email platform.
LiquiLens to StripeStripe is a payment processing platform for online businesses.
More into TicketCo
HubSpot to TicketCoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TicketCoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TicketCoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TicketCoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TicketCoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TicketCoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LiquiLens and TicketCo, answered
What can start an automation from LiquiLens?
Any of LiquiLens's 1 trigger in the catalog, including New flagged institution. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TicketCo when something happens in LiquiLens?
Any of TicketCo's 6 actions, including Find Customers, Get Event, Get Event Status and Get Membership. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TicketCo to LiquiLens?
Yes. When something happens in TicketCo, your agent can act in LiquiLens too. This page covers both directions: TicketCo's triggers and LiquiLens's actions are listed here as well.
Do I have to build a connector for LiquiLens or TicketCo?
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 LiquiLens and TicketCo 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.