Build solutions, not workarounds.
What do you want Zipzign and SMSAPI 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 Zipzign can start in SMSAPI
When New document created in Zipzign
then Add Blacklisted Number in SMSAPI
When Document signed in Zipzign
then Add Sender Name in SMSAPI
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 Zipzign and SMSAPI
Triggers and actions 2 triggers · 18 actions
Trigger
Document signedFires when every signer on a ZipZign signable document has signed (the document.signed webhook event). Other ZipZign events delivered to the same endpoint are ignored.
Trigger
New document createdFires when a document is created; delivered via the document.created webhook event.
Action
Add documentCreate a new document (readable, signable, or payable)
Action
Delete documentMarks a ZipZign document as deleted. Recipients then see a "no longer available" page. Documents that have been paid or signed cannot be deleted.
Action
Get documentFetches a document by ID, including its status, PDF link, signers, payment details and metadata. An error occurs if the document is not found.
Action
Submit signatureSubmits a signer's signature for a signable document using the signer's token from their signing link.
Action
Update documentReplaces a document's content (HTML, template or PDF) and resets it to its active status, or renames it when only a name is given.
Action
Verify integrityChecks whether a signed document has been tampered with by comparing its current SHA-256 hash to the one recorded at signing time.
Action
Add Blacklisted NumberAdds a phone number to the account's blacklist so no SMS messages are sent to it, optionally until an expiration date.
Action
Add Sender NameAdds a new sender name to the SMSAPI account. The name starts inactive until SMSAPI verifies it.
Action
Check HLR LookupChecks a mobile number against the HLR (Home Location Register). The lookup is accepted immediately; the detailed network result is sent to the HLR callback URL set in the SMSAPI Customer Portal.
Action
Create ContactCreates a contact in the SMSAPI contact database.
Action
Delete Blacklisted NumberRemoves a single number from the SMSAPI blacklist, so messages can be sent to it again.
Action
Delete ContactDeletes a contact from the SMSAPI contact database by its ID.
Action
Get Account BalanceReturns the current credit balance (points) and profile details of the connected SMSAPI account.
Action
List Blacklisted NumbersLists the phone numbers on the account's blacklist (numbers SMS sending is blocked to), with each entry's id, number, date added and expiration date.
Action
List Sender NamesLists every sender name on the SMSAPI account with its status (ACTIVE / INACTIVE), whether it is the default, and when it was created.
Action
Send Text MessageSends an SMS to one or more phone numbers through SMSAPI.
Action
Send Text Message to GroupSends an SMS to every contact in a group from the SMSAPI contacts database.
Action
Update ContactUpdates an existing contact in the SMSAPI contacts database. Only the fields you fill in are 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 Zipzign
Zipzign to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Zipzign to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Zipzign to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Zipzign to AnthropicAnthropic builds Claude, a family of large language models.
Zipzign to Google AnalyticsGoogle Analytics tracks and reports website traffic, user behavior, and conversion data, enabling marketers...
Zipzign to Google MapsIntegrate Google Maps to access location data, geocoding, directions, and mapping services in your...
More into SMSAPI
HubSpot to SMSAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SMSAPISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SMSAPISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SMSAPIGoogle Sheets
Gmail to SMSAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SMSAPIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Zipzign and SMSAPI, answered
What can start an automation from Zipzign?
Any of Zipzign's 2 triggers in the catalog, including New document created and Document signed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SMSAPI when something happens in Zipzign?
Any of SMSAPI's 12 actions, including Create Contact, Send Text Message, Send Text Message to Group and Update Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SMSAPI to Zipzign?
SMSAPI has no triggers in the catalog today, so automations start in Zipzign. If you need the other direction, ask: your agent reads SMSAPI's API documentation and adds it.
Do I have to build a connector for Zipzign or SMSAPI?
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.