Integration
Connect Open Government, South Australian Government to Didit
When something happens in Open Government, South Australian Government, your agent does the next thing in Didit. 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 Open Government, South Australian Government and Didit 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 Open Government, South Australian Government can start in Didit
When New or updated dataset in Open Government, South Australian Government
then Add business in Didit
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 Open Government, South Australian Government and Didit
Triggers and actions 1 trigger · 22 actions
- New or updated dataset
Fires when a dataset on the Data.SA portal is published or its metadata is updated.
- Find datasets
Search South Australian Government open datasets by keyword, tag, organisation, or format.
- Find records in a resource
Query rows from a tabular data resource (the datastore) with filters, full-text search, or SQL.
- Get dataset
Retrieve full metadata and resource list for one dataset by its ID or name.
- Get organisation
Retrieve details and dataset list for one publishing organisation.
- Get resource
Retrieve metadata for one data resource (file/table) belonging to a dataset.
- List datasets
List all dataset names published on the Data.SA open data portal.
- List groups
List the topical groups datasets are categorized under (e.g. Health, Transport, Environment).
- List organisations
List the government organisations that publish datasets on the portal.
- Add business
Create a Didit business (KYB) record.
- Add user
Create a Didit end-user record.
- Add webhook destination
Register a webhook destination URL to receive Didit events.
- Create Verification Session
Creates a new Verification Session
- Delete verification session
Delete a KYC or KYB verification session by id.
- Get business
Retrieve a Didit business record by vendor_data id.
- Get credit balance
Retrieve the account's remaining credit balance.
- Get user
Retrieve a Didit end-user record by vendor_data id.
- List businesses
List Didit business (KYB) records.
- List users
List Didit end-user records.
- List webhook destinations
List configured webhook destinations.
- Retrieve Verification Session
Retrieve a Verification Session
- Update business
Update a Didit business record.
- Update user
Update a Didit end-user record.
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 Open Government, South Australian Government
Open Government, South Australian Government to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Open Government, South Australian Government to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Open Government, South Australian Government to Google SheetsGoogle Sheets
Open Government, South Australian Government to StripeStripe is a payment processing platform for online businesses.
Open Government, South Australian Government to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Open Government, South Australian Government to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Didit
HubSpot to DiditHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to DiditGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DiditGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Open Government, South Australian Government and Didit, answered
What can start an automation from Open Government, South Australian Government?
Any of Open Government, South Australian Government's 1 trigger in the catalog, including New or updated dataset. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Didit when something happens in Open Government, South Australian Government?
Any of Didit's 14 actions, including Create Verification Session, Update business, Update user and Add business. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Didit to Open Government, South Australian Government?
Didit has no triggers in the catalog today, so automations start in Open Government, South Australian Government. If you need the other direction, ask: your agent reads Didit's API documentation and adds it.
Do I have to build a connector for Open Government, South Australian Government or Didit?
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.