Integration
Connect SOS Inventory to DistrictAPI
When New Customer fires in SOS Inventory, your agent runs Batch lookup districts in DistrictAPI. 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 SOS Inventory 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 SOS Inventory can start in DistrictAPI
When New Customer in SOS Inventory
then Batch lookup districts in DistrictAPI
When New Estimate in SOS Inventory
then Find districts by name, state or county 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 SOS Inventory and DistrictAPI
Triggers and actions 10 triggers · 34 actions
Trigger
New CustomerTriggers when a new customer is created.
Trigger
New EstimateTrigger
New InvoiceTriggers when a new invoice is created.
Trigger
New ItemTrigger
New Purchase OrderTriggers when a new purchase order is created.
Trigger
New Sales OrderTriggers when a new sales order is created.
Trigger
New Sales ReceiptTriggers when a new sales receipt is created.
Trigger
New ShipmentTriggers when a new shipment is created.
Trigger
New VendorTrigger
Updated Item QuantityTriggers when an item quantity is updated.
Action
Add estimate/api/v2/estimate. Creates an estimate.
Action
Add inventory adjustment/api/v2/adjustment. Creates an inventory adjustment.
Action
Add invoice/api/v2/invoice. Creates an invoice.
Action
Add item/api/v2/item. Creates an item (inventory, non-inventory, service, assembly, kit etc.).
Action
Add purchase order/api/v2/purchaseorder. Creates a purchase order.
Action
Add transfer/api/v2/transfer. Creates an inventory transfer between locations.
Action
Add vendor/api/v2/vendor. Creates a vendor.
Action
Create CustomerCreates a new customer
Action
Create Sales OrderCreates a new sales order
Action
Create Sales ReceiptCreates a new sales receipt
Action
Find CustomerFinds a customer
Action
Find Sales OrderFinds a sales order
Action
Find vendors/api/v2/vendor with query filters. Searches vendors.
Action
Get customer/api/v2/customer/{id}. Retrieves one customer by id.
Action
Get estimateReturns one estimate by id, including its lines and custom fields.
Action
Get inventory adjustmentReturns one inventory adjustment by id, including its lines.
Action
Get invoiceReturns one invoice by id.
Action
Get item/api/v2/item/{id}. Retrieves one item by id.
Action
Get purchase orderReturns one purchase order by id.
Action
Get sales order/api/v2/salesorder/{id}. Retrieves one sales order.
Action
Get sales receiptReturns one sales receipt by id, including its lines and custom fields.
Action
Get transferRetrieves a single inventory transfer by id, including its from/to locations and lines.
Action
List items/api/v2/item. Lists items with query filters and paging.
Action
Update customer/api/v2/customer/{id}. Updates a customer; requires syncToken.
Action
Update item/api/v2/item/{id}. Updates an item; requires current syncToken.
Action
Update sales order/api/v2/salesorder/{id}. Updates a sales order; requires syncToken.
Action
Batch lookup districtsLooks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one.
Action
Find districts by name, state or countyReturns the school districts matching the name, state or county you supply.
Action
Get districtReturns the full profile of one school district, including its address, grades served, enrollment, finances and boundary.
Action
Get schoolReturns the full profile of one school, including its address, grades served, enrollment and parent district.
Action
Get school's districtReturns the full profile of the school district a given school belongs to.
Action
List districtsReturns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID.
Action
List schoolsReturns the schools near a street address or a pair of coordinates, within the radius you choose.
Action
List schools by districtReturns 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 SOS Inventory
SOS Inventory to StripeStripe is a payment processing platform for online businesses.
SOS Inventory to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
SOS Inventory to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
SOS Inventory to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
SOS Inventory to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
SOS Inventory to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
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.
Salesforce to DistrictAPISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DistrictAPISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DistrictAPIGoogle Sheets
Gmail to DistrictAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
SOS Inventory and DistrictAPI, answered
What can start an automation from SOS Inventory?
Any of SOS Inventory's 10 triggers in the catalog, including New Customer, New Estimate, New Invoice and New Item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in DistrictAPI when something happens in SOS Inventory?
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 SOS Inventory?
DistrictAPI has no triggers in the catalog today, so automations start in SOS Inventory. 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 SOS Inventory 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.