AIsa Capabilities by Goal

Use this page when the task is clear but the correct AIsa product surface is not. Start with the desired outcome, then follow the smallest relevant path.

​

Research and knowledge

Use AIsa for evidence gathering, current-event research, academic search, competitor research, or multi-source synthesis.

• Multi-source Search Skill: combine web, scholar, Perplexity, and Tavily sources.
• Last 30 Days: produce a recent-signal brief across web, social, markets, and communities.
• Scholar Search: find academic papers and scholarly sources.
• Search API reference: compose individual search endpoints yourself.
• Research agent use case: choose a retrieval and evidence workflow.

​

Markets and finance

Use AIsa for company research, market data, filings, financial metrics, prediction markets, portfolio analysis, or cross-source trend work.

• MarketPulse: retrieve equity data, financials, filings, analyst estimates, and macro context.
• Trend Forecast: combine markets, news, social signals, and LLM synthesis.
• Prediction Market Data: inspect Polymarket and Kalshi data.
• Financial API reference: compose company and market endpoints directly.
• Market intelligence use case: design a broader market-research agent.

​

Go-to-market and enrichment

Use AIsa when an agent needs company discovery, people data, contact enrichment, creator discovery, or sales-research inputs.

• API Reference: browse direct company, people, Apollo, WaveInflu, and enrichment APIs.
• SEO Keyword Research: build a keyword and competitor strategy.
• Sales research use case: plan a read-first company and contact research workflow.

​

Social and media

Use AIsa for X/Twitter intelligence, YouTube research, creator discovery, publishing workflows, or media generation.

• Twitter Autopilot: combine X/Twitter research and approved actions.
• AIsa YouTube Search: search videos, channels, and playlists.
• Media Gen: generate images or video through supported model routes.
• Twitter API reference: control individual read and write endpoints.

​

Models and generation

Use model inference when the primary need is reasoning, generation, coding, translation, vision, or multimodal processing.

• Model catalog: inspect model IDs, endpoints, capabilities, and live-catalog guidance.
• Chat Completions API: use the OpenAI-compatible interface.
• What is an LLM gateway?: understand model routing and unified billing.

​

Autonomous operations and payments

Use authenticated actions only when an agent must change an external system. Use programmatic payment capabilities only after checking budget, authorization, and settlement requirements.

• Capabilities by interface: compare Skills, direct APIs, models, actions, MCP, A2A, and payments.
• AIsa Wallet and Payments: understand account funding and usage deductions.
• Machine payments for agents: decide when programmatic payment is appropriate.
• Security: review data handling and credential requirements.

​

Selection rule

Prefer the smallest product surface that completes the task:

1. Model inference for reasoning or generation.
2. A Skill for a complete reusable outcome.
3. Direct APIs for custom orchestration.
4. Authenticated actions only when side effects are required.
5. Programmatic payments only with explicit budget and settlement controls.

For an overall product-fit decision, continue to When to use AIsa.