Integration
Connect Moxie to DistrictAPI
When something happens in Moxie, your agent does the next thing in DistrictAPI. 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 Moxie and DistrictAPI 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 Moxie can start in DistrictAPI
When Client Created in Moxie
then Batch lookup districts in DistrictAPI
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 Moxie and DistrictAPI
Triggers and actions 30 triggers · 20 actions
- Agreement Sent
Triggers when a proposal is sent either via link or email.
- Agreement Signed
Triggers when an agreement is accepted and signed with e-signature.
- Agreement Viewed
Triggers when a user views the proposal.
- Client Created
Triggers when a new client is created in Moxie.
- Client Deleted
Triggers when a client record is deleted in Moxie.
- Client Updated
Triggers when a client record is updated in Moxie.
- Form Completed
Triggers when a form is completed.
- Invoice Sent
Triggers when an invoice is sent in Moxie.
- Meeting Cancelled
Triggers when a meeting is cancelled
- Meeting Scheduled
Triggers when a new meeting is scheduled
- Meeting Updated
Triggers when a meeting is updated or rescheduled
- Opportunity Created
Triggered with a pipeline opportunity is created
- Opportunity Deleted
Triggered with a pipeline opportunity is deleted
- Opportunity Updated
Triggered with a pipeline opportunity is updated
- Payment Received
Triggers when a payment is received either vial Stripe or manual entry.
- Project Completed
Triggers when a project is set to "complete" in Moxie.
- Project Created
Triggers when a new project is created in Moxie.
- Project Updated
Triggers when the settings for a project are updated.
- Task Approval
Triggers when a new Deliverable is ready for client approval.
- Task Created
Triggered when a Project Task is created
- Task Deleted
Triggered when a Project Task is deleted
- Task Updated
Triggered with a Project Task is updated.
- Ticket Closed
Triggers and a support ticket is closed
- Ticket Comment
Triggers when a comment is created on a ticket
- Ticket Created
Triggers when a new support ticket is created
- Ticket Deleted
Triggers when a support ticket is deleted
- Ticket Updated
Triggers when a support ticket is updated
- Time Worked Created
Triggers when a new time worked entry is created.
- Time Worked Deleted
Triggers when a time worked record is deleted.
- Time Worked Updated
Triggers when a time worked entry has been updated.
- Create Client
Creates a new client record in Hectic
- Create Expense
Records a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.
- Create Opportunity
Create a new pipeline opportunity
- Create & Optionally Send Invoice
Creates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.
- Create or Update Calendar Event
Create or update a calendar event in Moxie
- Create Project
Create a project and optionally use a template
- Create Task
Create a task in the project management system
- Create Ticket
Create a Ticket for a client and contact
- Create Ticket Comment
Adds a comment (public or private) to an existing ticket.
- Create Time Worked
Creates a time worked entry
- Delete Calendar Event
Deletes a calendar event in Moxie by the external ID.
- Find a Client
Finds a client by either name or contact email address.
- Batch lookup districts
Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one.
- Find districts by name, state or county
Returns the school districts matching the name, state or county you supply.
- Get district
Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary.
- Get school
Returns the full profile of one school, including its address, grades served, enrollment and parent district.
- Get school's district
Returns the full profile of the school district a given school belongs to.
- List districts
Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID.
- List schools
Returns the schools near a street address or a pair of coordinates, within the radius you choose.
- List schools by district
Returns the open schools inside a given school district, optionally limited to one school type or to charter schools.
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 Moxie
Moxie to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Moxie to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Moxie to Google SheetsGoogle Sheets
Moxie to StripeStripe is a payment processing platform for online businesses.
Moxie to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Moxie to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into DistrictAPI
Arxiv to DistrictAPIOpen-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...
HubSpot to DistrictAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to DistrictAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Moxie and DistrictAPI, answered
What can start an automation from Moxie?
Any of Moxie's 30 triggers in the catalog, including Client Created, Client Updated, Form Completed and Meeting Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in DistrictAPI when something happens in Moxie?
Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DistrictAPI to Moxie?
DistrictAPI has no triggers in the catalog today, so automations start in Moxie. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it.
Do I have to build a connector for Moxie or DistrictAPI?
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.