--- author: OOMOL author_url: https://oomol.com/about/ datePublished: 2026-09-29 title: "AIsa Is Now in OOMOL: Public Data Reads for Agents, Next to Your Work Apps" description: "OOMOL and OpenConnector now officially support AIsa: 106 read Actions for web traffic, SEO, financial, crypto, social and company data, with OOMOL credits or your own AIsa key." lang: en canonical_url: https://oomol.com/blog/aisa-oomol-partnership/ markdown_url: https://oomol.com/blog/aisa-oomol-partnership.md --- ![AIsa public-data Actions and authorized work-app connections meet in the OOMOL connection gateway](/blog/aisa-oomol-partnership/en-cover.webp) AIsa is now officially supported in OOMOL and the open-source OpenConnector runtime. [AIsa](https://aisa.one/) describes itself as a capability layer for the agentic economy: APIs, data and models under one key. Through this partnership, an agent connected to OOMOL can read public market data from AIsa, including website traffic, search rankings, company filings, social posts and prediction markets, and then act on the findings in apps you have connected, such as Notion, Slack or Gmail. In OOMOL's hosted service, AIsa works without an AIsa account. It ships with a built-in connection that bills to your OOMOL credits. Teams running OpenConnector themselves can connect an OOMOL Key in the Web Console to use the same built-in account, or enter their own AIsa API key, and call the same Action ids. AIsa's [announcement](https://aisa.one/blog/aisa-oomol-partnership) sums up the idea as "public-data reads meet OAuth writes." This article covers the OOMOL side: what the integration exposes, how it fits the gateway, and how to run a first call. ## What AIsa adds to OOMOL The AIsa provider in OpenConnector has the service id `aisa` and exposes **106 Actions**. All of them are read operations. They group by data source: | Source | What an agent can read | Example Action ids | | --- | --- | --- | | Similarweb (23) | Website visits and engagement, traffic trends, marketing channels, referrals, audience and top geographies | `get_similarweb_traffic_snapshot`, `get_similarweb_traffic_trend`, `get_similarweb_top_geographies` | | Semrush (17) | Domain rank and organic keyword totals, keyword difficulty, backlinks, organic competitors | `get_semrush_domain_overview`, `compare_semrush_domains`, `get_semrush_backlinks_overview` | | Financial data (14) | Stock prices, company facts, income statements, SEC filings, insider trades, analyst estimates, company news | `get_stock_prices`, `list_company_filings`, `get_insider_trades` | | Crypto markets (11) | Coin and token prices, market charts, exchanges, trending coins, crypto news | `get_crypto_prices`, `get_crypto_market_chart`, `get_trending_crypto` | | X / Twitter (10) | Public posts, user timelines, replies, threads, trends | `search_twitter_posts`, `get_twitter_user_timeline`, `get_twitter_trends` | | Apollo (9) | Company and people enrichment, organization search, job postings, company news | `enrich_apollo_organization`, `search_apollo_people`, `get_apollo_job_postings` | | DataForSEO (8) | How domains and keywords appear in ChatGPT, Claude, Gemini and Perplexity answers, plus AI-search volume | `get_dataforseo_llm_mention_metrics`, `search_dataforseo_llm_mentions`, `query_dataforseo_chatgpt` | | Creators and ads (7) | Foreplay ad library search, brand ads and analytics, creator search | `search_foreplay_ads`, `get_foreplay_brand_ads`, `find_similar_creators` | | Prediction markets (5) | Kalshi and Polymarket markets, trades, events and activity | `get_kalshi_markets`, `get_polymarket_markets` | Two more Actions, `get_credits_balance` and `get_usage`, report the AIsa account's balance and usage. The catalog above is what the connector exposes today. AIsa's own platform offers more resources, and a capability listed on aisa.one is available through OOMOL only once it appears as an Action in this provider. ## Where AIsa fits in the gateway Most useful agent tasks combine two kinds of access. **Reads from outside sources.** Market research needs information your team does not own: how much traffic a competitor gets, which keywords it ranks for, what people post about a product launch. AIsa supplies this through one key. **Writes into your own systems.** The result of that research has to land somewhere: a Notion page, a Slack channel, a Gmail draft, a HubSpot record. Those writes require you to connect each app with your own authorization. OOMOL runs both kinds of connection through one runtime. For an agent, an AIsa Action and a Notion Action are called the same way, with the same discovery tools and schema-described inputs and outputs. For the team operating it, the same controls apply to both: - **Connection identity.** Each connection carries a safe account label, so an agent can see which account an Action will run as. Named connections let you keep several accounts for one app and pick one per call (`x-oo-connector-alias` on HTTP, `connectionName` in MCP). - **Action policies.** In OpenConnector, runtime tokens can carry `allowedActions`, `blockedActions` and `allowedConnections` grants. A research token can be limited to `aisa.*` and a single Notion account. In the OOMOL Console, each connection has permission groups; the Team default is "All Actions available", and you can narrow it. - **Redacted run logs.** Each call is recorded with credentials removed, so you can trace what ran and why it failed. - **Keys stay behind the boundary.** The AIsa key, or OOMOL's built-in credential, and your OAuth tokens stay inside the runtime. The agent process never receives them. Self-hosted deployments can encrypt stored credentials. The two sides stay separate. The AIsa key and OOMOL credits give no access to your work apps. Connecting a work app gives the agent technical access, and connecting it does not add an approval step. If a write should wait for a person, the workflow or product has to define that review. AIsa's post makes the same point. ## Two ways to connect AIsa | | OOMOL hosted | Self-hosted OpenConnector | | --- | --- | --- | | Credential | OOMOL built-in account by default; you can also add your own AIsa key | An OOMOL Key for the built-in account, or your own AIsa API key from [console.aisa.one](https://console.aisa.one) | | Billing | OOMOL credits, as part of [One Key Plan](/blog/one-key-plan/); see "View pricing" on the connection page | OOMOL credits with an OOMOL Key, or your AIsa account with your own key | | Setup | None for the built-in account | In the Web Console: **Marketplace > Connect OOMOL Key**, or open AIsa under **Providers** and enter an API key | | How agents call it | oo CLI, [Connector SDK](/docs/connector-sdk/) | MCP at `/mcp`, HTTP `/v1/actions/aisa.`, Connector SDK, oo CLI | | Who operates the runtime | OOMOL | Your team, under the Apache-2.0 license | **OOMOL hosted.** Open [App Connections > AIsa](https://console.oomol.com/connections/aisa) in the OOMOL Console. The default connection is the "OOMOL built-in account", and the Console notes: "No account setup required. Calls use OOMOL credits." Per-call pricing is shown in the Console under "View pricing". If you already have an AIsa account, choose "Add account" and enter your own key. **Self-hosted OpenConnector.** Everything is set up in the runtime's Web Console. There are two options: - **OOMOL Key.** Open **Marketplace**, choose **Connect OOMOL Key**, and paste a key from the [OOMOL Console](https://console.oomol.com/api-key). AIsa then shows "Supports OOMOL Key" and runs through the built-in account, billed to your OOMOL credits. This is the same key that unlocks the other compatible services in the Marketplace. - **Your own AIsa key.** Open AIsa under **Providers** and enter an API key from [console.aisa.one](https://console.aisa.one). The key stays on your gateway. Agent hosts can then use the MCP tools `list_apps`, `list_connections`, `search_actions`, `get_action_guide` and `execute_action`, or call an Action directly at `POST /v1/actions/aisa.get_similarweb_traffic_snapshot`. The [self-hosting guide](/docs/openconnector-self-hosting/) covers Docker, source and Cloudflare deployments, including credential encryption. ## A real call: github.com traffic Here is one call made through OOMOL hosted on September 29, 2026 (UTC): ```bash oo connector run aisa -a get_similarweb_traffic_snapshot \ -d '{"domain":"github.com","country":"ww"}' ``` Selected fields from the response, with decimals rounded: ```text month 2026-08 visits 636913004 pages_per_visit 5.81 bounce_rate 0.388 average_visit_duration 391 source similarweb meta.appId marketplace:oomol:aisa ``` GitHub had roughly 636.9 million worldwide visits in August 2026, with about 5.8 pages and six and a half minutes per visit. `meta.appId` matches the Connection ID of the OOMOL built-in AIsa account shown in the Console. On the same day, a Semrush US domain overview for github.com returned a rank of 117 and 6,346,227 organic keywords. This is a single call on one date, shown to illustrate the input and output shape. It is not a benchmark of latency, coverage or data accuracy. ## Assemble a weekly market brief AIsa's announcement suggests three workflows: customer research saved as a Notion brief, competitive signals turned into tasks, and company research turned into an email draft. [Read them in AIsa's post](https://aisa.one/blog/aisa-oomol-partnership). Here is a fourth one to assemble yourself. It is a workflow you build from available Actions, not a prebuilt automation. **Goal:** every Monday, a short brief on how your product and two competitors moved last week, saved in Notion and summarized in Slack after someone reviews it. 1. **Traffic.** Call `aisa.get_similarweb_traffic_snapshot` and `aisa.get_similarweb_traffic_trend` for each domain. 2. **Search.** Call `aisa.get_semrush_domain_overview`, or `aisa.compare_semrush_domains` for keyword overlap. 3. **Conversation.** Call `aisa.search_twitter_posts` with each product name to collect notable public posts, keeping the post links. 4. **Draft.** The agent writes the brief: numbers with their source and data period, then its interpretation, labeled as such. Missing data stays missing. 5. **Save.** `notion.create_page` saves the brief in a drafts area, using your Notion connection. 6. **Review.** A person reads the draft and approves it or edits it. Your workflow defines this step. 7. **Share.** After approval, `slack.post_message` posts a summary with the Notion link, using your Slack connection. To keep the scope tight on a self-hosted runtime, give the research step a token that allows only `aisa.*` and `notion.create_page`, and use a separate token for the Slack post. Scheduling the Monday run requires your own scheduler or workflow runner; connecting the apps does not schedule anything. Each run makes several AIsa calls. Start with one domain and check the usage in the Console before adding competitors. ## Getting started 1. **Hosted:** sign in to the [OOMOL Console](https://console.oomol.com/) and open [App Connections > AIsa](https://console.oomol.com/connections/aisa). The built-in account is ready to use. Check "View pricing" first. 2. **Self-hosted:** in your OpenConnector Web Console, connect an OOMOL Key under **Marketplace**, or enter your own AIsa key on the AIsa provider page. 3. Ask your agent to search AIsa Actions for the data you need, or run a single Action with the oo CLI. 4. Connect the destination apps, such as Notion, Slack, Gmail or HubSpot, with their own authorization, and allow only the Actions the workflow needs. See [access control](/docs/access-control/). 5. Run one question end to end and review the output before expanding it. ## Research and action in the same runtime AIsa brings a broad set of public market data under one key. OOMOL provides the connection layer where that data meets the accounts your team already works in, with the same identity, policy and logging for both. The gateway is also open source. On September 29, 2026, OOMOL's [public catalog](https://connector.oomol.com/v1/catalog) listed **1,566 providers and 18,267 Actions**, and the [OpenConnector repository](https://github.com/oomol-lab/open-connector) had **5,911 Stars and 524 Forks**. You can read the AIsa provider definition and its Action schemas in `src/providers/aisa/`. **[Open AIsa in the OOMOL Console](https://console.oomol.com/connections/aisa), run one research question, and send the result to an app you have connected.** --- *Sources and scope: This article uses AIsa's partnership post (dated September 24, 2026), the OpenConnector repository and documentation, the OOMOL Console AIsa connection page, and catalog and GitHub data checked on September 29, 2026 (UTC). Action counts come from the `aisa` provider source. The github.com figures come from single calls on September 29, 2026 and are shown as examples, not benchmarks. The weekly brief is a workflow you assemble; it is not a prebuilt OOMOL or AIsa automation. Prices are not stated because they are shown in the Console and may change.*