Wit.ai
32 operations0 webhooks
Natural language understanding platform for intent detection and conversational app building.
Supported operations
- Create AppWrite
Create a new Wit.ai app
- Delete AppDestructive
Delete a specific Wit.ai app
- Export AppRead-only
Export Wit.ai app data as a ZIP backup
- Get AppRead-only
Retrieve metadata and settings of a Wit.ai app
- List AppsRead-only
List all Wit.ai apps for the authenticated user
- List TagsRead-only
List all tag groups (versions) for a Wit.ai app
- Update AppWrite
Update an existing Wit.ai app
FAQ
Install corsair and @corsair-dev/witai, add the Wit.ai plugin, and connect with an API key. Then call methods like corsair.witai.api.apps.createApp() from your app. Corsair syncs data per tenant.
Yes. Wit.ai requires an API key from your Wit.ai account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Wit.ai, GitHub, Notion, Stripe, and the rest. Trigger Wit.ai from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for natural language understanding platform for intent detection and conversational app building. Common builds include sync jobs, admin tooling, and agents that call Wit.ai APIs from your backend. Local DB entities let you query synced Wit.ai records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Wit.ai API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/witai in the open repo. When Wit.ai ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Wit.ai data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Wit.ai data on your behalf.