Integration
Connect Frihet to NameAPI
When New Expense fires in Frihet, your agent runs Detect contact risk in NameAPI. 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 Frihet and NameAPI 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 Frihet can start in NameAPI
When New Expense in Frihet
then Detect contact risk in NameAPI
When New Expense in Frihet
then Detect disposable email address in NameAPI
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 Frihet and NameAPI
Triggers and actions 1 trigger · 44 actions
Trigger
New ExpenseFires when a new expense is created. Backed by vendor webhook registration.
Action
Add ClientCreate a client.
Action
Add DepositCreate a deposit.
Action
Add ExpenseCreate an expense.
Action
Add InvoiceCreate an invoice.
Action
Add ProductCreate a product.
Action
Add QuoteCreate a quote.
Action
Add VendorCreate a vendor.
Action
Apply deposit to invoiceApply a deposit balance to an invoice.
Action
Delete ClientDelete a client.
Action
Delete ExpenseDelete an expense.
Action
Delete InvoiceDelete an invoice.
Action
Delete ProductDelete a product.
Action
Delete QuoteDelete a quote.
Action
Delete VendorDelete a vendor.
Action
Get ClientRetrieve a client by id.
Action
Get DepositRetrieve a deposit by id.
Action
Get ExpenseRetrieve an expense by id.
Action
Get InvoiceRetrieve an invoice by id.
Action
Get ProductRetrieve a product by id.
Action
Get QuoteRetrieve a quote by id.
Action
Get VendorRetrieve a vendor by id.
Action
List ClientsList clients.
Action
List DepositsList deposits.
Action
List ExpensesList expenses.
Action
List InvoicesList invoices.
Action
List ProductsList products.
Action
List QuotesList quotes.
Action
List VendorsList vendors.
Action
Mark invoice as paidMark an invoice as paid.
Action
Send InvoiceSend invoice by email to the client.
Action
Send QuoteSend quote by email to the client.
Action
Update ClientPartial update a client.
Action
Update ExpensePartial update an expense.
Action
Update InvoicePartial update an invoice.
Action
Update ProductPartial update a product.
Action
Update QuotePartial update a quote.
Action
Update VendorPartial update a vendor.
Action
Detect contact riskRisk Detector: scores a person/email/address record for fake or risky data.
Action
Detect disposable email addressDisposable Email Address Detector: checks whether an email is disposable.
Action
Format person nameName Formatter: formats a person name (e.g. salutation/full name) per locale.
Action
Genderize person nameName Genderizer: infers gender from a person name.
Action
Match person namesName Matcher: compares two person names and returns a match type/confidence.
Action
Parse email nameEmail Name Parser: extracts a person name from an email address.
Action
Parse person nameName Parser: splits a full name into components (given/family names, title, gender).
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 Frihet
Frihet to PredictHQEvents and natural disasters data
Frihet to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Frihet to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Frihet to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Frihet to Google SheetsGoogle Sheets
Frihet to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into NameAPI
HubSpot to NameAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NameAPISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NameAPISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NameAPIGoogle Sheets
Gmail to NameAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NameAPIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Frihet and NameAPI, answered
What can start an automation from Frihet?
Any of Frihet's 1 trigger in the catalog, including New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in NameAPI when something happens in Frihet?
Any of NameAPI's 7 actions, including Detect contact risk, Detect disposable email address, Format person name and Genderize person name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from NameAPI to Frihet?
NameAPI has no triggers in the catalog today, so automations start in Frihet. If you need the other direction, ask: your agent reads NameAPI's API documentation and adds it.
Do I have to build a connector for Frihet or NameAPI?
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.