Let your agent act in the apps your users connect
Your users connect Shopify, Gmail and 1,600+ other apps once, your agent acts in their accounts on the AIsa key and balance you already use, and you never store an OAuth token.
One request runs an action in a user's account
Name the action, the end user and the input. AIsa picks that user's connection, checks the input against the action's schema and returns the app's answer.
15 apps verified for production
Example · fictional merchant store_8812
Every end user has their own connections
A connection belongs to your account and one externalUserId, so a run for one user never touches another user's accounts.
Billed per successful run
Each successful run costs $0.0003 on every plan. Failed runs, browsing apps, connecting and managing connections cost nothing.
apps your users can connect
actions across those apps
per 1,000 successful runs
to browse, connect and manage
The work you skip for every app
Each app your users connect normally needs its own OAuth app, token store, API client and error handling, and AIsa Connect covers them with one API on your AIsa key.
| For each app | On your own | With AIsa Connect |
|---|---|---|
| Sign-in | Register an OAuth app with the platform | Users sign in on a page AIsa hosts |
| Credentials | Store and protect every user's tokens and keys | AIsa holds them, and you keep a user ID |
| API client | Write and maintain one per app | One request runs any action |
| Input checks | Hand-written for each API | Every action publishes its schema |
| Per-user access | Enforced in your own code | Each connection belongs to one user |
| Errors | A different format for each API | One format that names who fixes it |
- Sign-in
- On your own
Register an OAuth app with the platform - With AIsa Connect
Users sign in on a page AIsa hosts - Credentials
- On your own
Store and protect every user's tokens and keys - With AIsa Connect
AIsa holds them, and you keep a user ID - API client
- On your own
Write and maintain one per app - With AIsa Connect
One request runs any action - Input checks
- On your own
Hand-written for each API - With AIsa Connect
Every action publishes its schema - Per-user access
- On your own
Enforced in your own code - With AIsa Connect
Each connection belongs to one user - Errors
- On your own
A different format for each API - With AIsa Connect
One format that names who fixes it
Three requests from catalog to result
Look up an action and its schema, have your user connect the app, and run the action for that user on your AIsa key.
- 1
Find the action
Search an app's actions, then read each one's input schema and whether it reads, writes or deletes.
GET /apps/shopify/actions?q=order - 2
Your user connects the app
Send OAuth apps to the page AIsa hosts, or forward the fields a key-based app needs, such as a Shopify token and store domain.
POST /connect/shopify/credentials - 3
Run it for that user
Send the action key, the user's externalUserId and the input. The response carries the result, the run id and the cost.
POST /actions/run
Tasks you can build on AIsa Connect
Each page shows the requests in order, the apps they use and a prompt that starts the build in your coding agent.
Build a Shopify AI agent
Merchants connect their store once, and your agent reads orders and stock and tags orders through AIsa Connect.
Build an AI customer support agent
Read order questions from a merchant's Gmail, look up each order in their store and draft the reply for a person to send.
Automate ecommerce reports
Pull each merchant's orders and email campaigns every week and write the report to their Notion.
Two ways your users connect an app
OAuth apps go through a page AIsa hosts, apps that take a key or store credentials connect through your own form, and both end in the same kind of connection.
A hosted page for OAuth apps
Start a connect session for the user, open its link and poll the session until it completes. The link expires after 30 minutes, and your server never sees an OAuth token.
Your own form for keys and store credentials
Collect the fields the app lists, such as a Shopify Admin API token and shop domain, and forward them once. AIsa checks the fields first, then the app checks the credentials.
Apps verified for production
These apps are tested end to end in production, and the catalog lists 1,684 apps with 21,356 actions in all.
Browse all 1,684 appsGoogle apps connect with read access today. An app joins this list once its connection works in production.
Safeguards for agents that act for your users
Each user's accounts stay apart, every input is checked before it reaches the app, writes never repeat on their own, and each error says who has to fix it.
- One user never reaches another's accounts
- A connection belongs to your account and one externalUserId. A run uses only that user's connection.
- Reads and writes are labeled
- Every action says whether it reads, writes or deletes, so your agent can ask a person before it changes anything.
- Input checked against the schema
- AIsa validates the input before the call. A bad field returns 422 validation_failed and nothing reaches the app.
- Writes never repeat on their own
- AIsa sends each run once, so a write never happens twice by accident. If one ends in outcome_unknown, check the app before you run it again.
- Errors name who fixes them
- Each error says whether the user, the app or AIsa caused it, so your product knows when to ask the user to reconnect.
- Access ends with one request
- When a user leaves or asks, delete their connection. It drops out of every list, and no later run can use it.
Questions about AIsa Connect
What it is, what it costs and how it keeps your users' accounts apart.
For anything else, talk to us.
For anything else, talk to us.
Connect your users' apps to your agent
Create a key in the console, connect a test account and run your first action at $0.0003 per successful run.