Connect your app’s API in minutes. No developer needed.
Paste your API endpoints into Aimate. Kaku, your AI coworker, can then look things up and take actions inside your CRM or web app for each signed-in user, with that user’s own permissions.
✓ No SDK✓ No backend changes✓ No API keys storedThree steps. Then your team just asks.
[02] How it works- STEP 01
Paste your endpoints
Copy a cURL command from your browser or Postman, fill in a URL with a sample payload, or upload your OpenAPI / Swagger file. Add several endpoints at once.
curl https://app.yourcrm.com/api/deals \ -G -d state=TX -d owner=me \ -H 'Accept: application/json' - STEP 02
Aimate turns them into tools
For each endpoint, Aimate drafts a tool: what it does, which inputs it needs, and whether it reads or changes data. Check the wording, adjust anything you like, and save.
list_open_dealsREADS DATALists the signed-in user’s open deals, filtered by state.inputs: state (text), owner (me | team) - STEP 03
Your team just asks
The chat inside your app can now use them. The AI coworker calls your API and answers with your real data, in plain language.
Show me my open deals in Texas.Create a follow-up task for Acme tomorrow.
Powerful for your team. Safe by design.
[03] Why teams like itNo code, no developer
If you can copy a request from Postman or your API docs, you can connect it. No SDK to install and no backend changes.
Every user sees only their own data
Calls run in the signed-in user’s own browser session, so your app applies its usual permissions. A sales rep sees their accounts; a manager sees the team’s.
Nothing changes without a yes
Anything that creates, updates or deletes data shows the user a Confirm / Cancel card first.
No API keys stored with Aimate
Any key or token in what you paste is removed automatically. The user’s existing login is used instead.
You stay in control
Approve, edit, turn off or remove any connection. Every action is logged with who asked, what ran and how it went, and the activity log downloads as CSV.
Works with what you already have.
[04] Supported formatscURL commands
Copied from your browser’s dev tools, Postman or your API docs
REST endpoints
Any URL with a sample JSON payload
OpenAPI 3 & Swagger 2
Upload the spec as JSON or YAML
Your existing login
Cookie sessions or browser access tokens, with CSRF support
Connect up to 30 endpoints per workspace. Already using Aimate on your website? Your public website chat keeps working as before.
01Do I need a developer to set this up?
No. Paste your endpoints, review the tools Aimate drafts and save. The only code is the Aimate chat script tag your app already has.
02Can the AI coworker see data a user isn't allowed to see?
No. Every request goes from that user's browser with their own login, so your app decides what they can see or change, exactly as it does today.
03Does Aimate store our API keys?
No. Any key or token in what you paste is stripped out automatically. For apps that use access tokens, you only tell Aimate where the token is kept, and it's read in the user's browser when needed.
04Can the coworker change data on its own?
No. Anything that creates, updates or deletes data asks the user to confirm first, and you can turn off any connection at any time.
05How many endpoints can I connect?
Up to 30 per workspace.
06Where does the AI coworker work?
Inside your own web app, where your users are signed in, such as your CRM or customer portal. Your public website chat keeps working as before.
Give your team a coworker that already knows your app.
See your own endpoints turned into tools in a 30-minute demo.