AIsa vs Jetty (2026)

The catalog puts thousands of APIs behind a single AIsa key, covering search, finance, social, company and people data and SaaS tools, served over REST and an MCP server. The server's five tools (list_categories, search, get_details, use and batch_use) reach 950+ APIs, with write actions such as Twitter Autopilot's approved actions and the Gmail and Notion Skills. Writes may need OAuth or an account connection for each capability.

SourceAIsa, aisa.one/llms.txt (MCP), aisa.one/docs llms-full.txt (Architecture, Security Evaluation Guide) and the homepageread 2026-09-25

Each workload runs in a sandbox with a coding agent, a model and the integrations it needs, with one integration on the free plan and ten on Squadron Platform, plus webhooks. Integrations are credentials injected into every run as environment variables for Slack, databases, GitHub, CRMs or the customer's own app, which the agent then uses through its own tools. There is no native connector catalog with defined read or write actions.

SourceJetty, jetty.io pricing, homepage and llms.txtread 2026-09-21

A Skill packages instructions, tool selection and workflow steps that the customer's own agent follows. Choosing between a Skill and the direct API comes down to who owns orchestration, the agent or the application, and AIsa itself runs no workflow. The batch_use tool runs several calls in one request without putting them in sequence. The Foundry card offers preconfigured OpenClaw instances, an open source runtime AIsa hosts but did not build, with no detail beyond the card.

Sourceaisa.one/docs/llms-full.txtread 2026-09-25

Workflows chain prebuilt actions in an ordered list of steps, and each action does one piece of work with no agent in the loop. Path expressions wire the steps together by reading earlier steps' outputs, and control flow actions include a fan out that starts a child run for each item in a list. A runbook hands a whole job to an agent in the same system, so the platform carries the control flow across steps and mixes deterministic steps with agent steps.

SourceJetty, jetty.io/docs/reference/api/stepsread 2026-09-21

Work starts only when an agent or application sends a request, since AIsa is a gateway that callers invoke. AIsa names no schedule, webhook or event source. The Telegram, Discord and Slack deployment belongs to OpenClaw, the open source runtime behind the Foundry card, and is configured per channel in OpenClaw.

SourceAIsa, aisa.one/docs llms-full.txt (Architecture, Use AIsa in OpenClaw)read 2026-09-25

Workloads run on a schedule as well as manually, from the terminal or through the API, and paid plans add webhooks, so work reaches the agent without a person starting it. Jetty supports scheduled workloads and offers a guide to running a runbook on a cron cadence.

SourceJetty, jetty.io/pricing and homepageread 2026-09-21

The search, crawl and research APIs AIsa resells, such as Tavily, Exa and Perplexity, query the public web, not the customer's corpus. The Jina embedding and rerank endpoints are building blocks a customer can use to make an index. AIsa maintains no index and offers no retrieval over the customer's own knowledge.

SourceAIsa, aisa.one/docs llms-full.txt (Search APIs, Create Embeddings, Rerank Documents)read 2026-09-25

A runbook carries the job and its checks, and integrations pass credentials for the customer's systems into each run, so knowledge reaches the agent in each run through its own tools. There is no document ingestion, index or retrieval store over the customer's knowledge.

SourceJetty, jetty.io/docs/get-started and llms.txtread 2026-09-21

Requests pass from the agent to an AIsa endpoint to the upstream capability and back, and AIsa adds no memory layer in that path. State handling is left to the application. The usage log records activity.

SourceAIsa, aisa.one/docs llms-full.txt (Architecture and Integration Boundaries)read 2026-09-25

Every run's configuration and trajectory is stored, and what runs reveal feeds edits to the runbook. That is a record of runs and of improvements absorbed into the runbook, not a memory layer the agent reads across runs, and there is no memory with a stated scope or lifetime.

SourceJetty, jetty.io homepage and docs/get-startedread 2026-09-21

The MCP server's get_details returns what an operation costs and a suggested maximum, and use and batch_use take max_price_usd and refuse anything above it before any charge. Each API key carries its own spending quota, capped at the wallet balance, and the customer sets these spend caps. AIsa's guidance tells the customer's agent to present scope and cap, get explicit approval and never run a paid call in the planning turn. The agent's host carries out that approval, and AIsa ships no approval surface of its own.

SourceAIsa, aisa.one/llms.txt (MCP) and aisa.one/docs llms-full.txt (Authentication, Machine Payments for AI Agents)read 2026-09-25

People decide which tasks become workloads, investigate finished runs and edit the runbook for the next run. Jetty lists adding guardrails as a way to improve a workload but describes no mechanism. There is no approval step, consent checkpoint, escalation rule or pause for a person's sign off during a run.

SourceJetty, jetty.io homepage and docs/get-startedread 2026-09-21

Keys are scoped by their own spending quotas and meant to be used one per service or environment. Dashboard sign in supports Google and GitHub OAuth, and AIsa advises SSO so revocation follows the identity provider. MCP clients sign in with OAuth tokens that can each be revoked. AIsa names no roles, organization permissions, attestation or certification. The Enterprise plan offers zero data retention, a custom MSA and DPA, and advanced access controls, without further detail.

SourceAIsa, aisa.one/docs llms-full.txt (Authentication, Security Evaluation Guide) and aisa.one/pricingread 2026-09-25

Squadron Platform adds roles and permissions and unlimited API keys, and API credentials are obtained and revoked through OAuth. The volume plan lists custom SLA, SOC 2 and HIPAA and single tenant options as a contractual offering, with no report, auditor or date published, and Jetty links no trust center.

SourceJetty, jetty.io/pricing and llms.txtread 2026-09-21

Console Usage and Logs shows summary cards, a usage trend and a split by model, plus a table per request showing the model or API, cost, cache hits and status, filterable by key. Each MCP use call reports what it actually spent. Calls appear one at a time, and no view ties them into an agent run or shows the steps and reasoning between them.

SourceAIsa, aisa.one/docs llms-full.txt (Usage Logs, Authentication) and aisa.one/llms.txt (MCP)read 2026-09-25

Jetty tracks everything the agent does in its managed sandbox. It records every step and the outputs of each run, with a workload report on how well the agent performed, and surfaces costs and errors for investigation. Each run is captured end to end, with every step's inputs, outputs, files and status.

SourceJetty, jetty.io/docs/get-started, homepage and llms.txtread 2026-09-21

A hosted gateway runs at api.aisa.one. On request, the Enterprise plan offers dedicated compute and custom infrastructure built around the customer's deployment model and compliance requirements. AIsa names no region list, customer environment option or way to select one.

SourceAIsa, aisa.one/pricing (Enterprise) and aisa.one/docs llms-full.txt (Architecture)read 2026-09-25

Standard plans run workloads in Jetty's managed sandboxes. The volume plan offers single tenant options, and Jetty invites customers to discuss flexibility on data residency and deployment, including single tenant cloud. There are no named regions, customer environment option or region selection.

SourceJetty, jetty.io/pricingread 2026-09-21

The Skills catalog holds 40+ installable Skills, each handling a complete task, such as SEO Keyword Research, KOL Creator Discovery, MarketPulse, Twitter Autopilot and Prediction Market Arbitrage. AIsa also ships ready made agents, such as AIsa CIO, an investment agent, and AIsa Labs templates for marketing, research and SEO. The Skills library arrived with the Bundled Skills System.

Sourceaisa.one/.well-known/agent-card.jsonread 2026-09-25

The Jetty Runbook Directory lets a customer pick a published runbook and run it from their own account with nothing to install, and runbooks can be written, published and shared. Each runbook is a whole workload that sets its own job, what counts as done and its checks.

SourceJetty, jetty.io/docs/get-started and pricingread 2026-09-21

The model gateway at api.aisa.one/v1 is OpenAI compatible and exposes 110+ models through the model catalog, from OpenAI, Anthropic, Gemini, DeepSeek, xAI, Moonshot and others, with native routes for Claude and Gemini. The caller picks the model on every request. With OpenClaw, a customer can set fallback chains and a different model per channel.

SourceAIsa, aisa.one/docs llms-full.txt (OpenAI Chat, Model catalog, Use AIsa in OpenClaw) and the homepageread 2026-09-25

Customers pick the agent and model pair for each workload, and Jetty says it works with any model. Every paid plan lets customers bring their own provider keys, billed by the provider, and Squadron Platform adds the option to bring your own AI gateway, so the customer controls model choice.

SourceJetty, jetty.io/pricing and homepageread 2026-09-21

An OpenAPI 3.1 specification covers the model and data endpoints (api.aisa.one/v1 and /apis/v1), with Bearer key auth. AIsa works with the OpenAI SDKs by swapping the base URL, ships a CLI, and publishes an Agent Card naming Bearer and x402 auth. Its MCP server (mcp.aisa.one, OAuth with dynamic client registration) is listed in the official MCP Registry.

SourceAIsa, aisa.one/llms.txt (Machine-Readable Resources, MCP), aisa.one/.well-known/agent-card.json and aisa.one/docs llms-full.txt (Authentication)read 2026-09-25

Apps connect to Jetty through an API, a TypeScript Client SDK and an MCP server, with API keys on every plan. The tasks API deploys, runs and monitors workloads, and a chat completions layer is compatible with OpenAI.

SourceJetty, jetty.io/docs/get-started, pricing and llms.txtread 2026-09-21

The Model Playground lets a person try a model with adjustable parameters and inspect payloads, and a model comparison page sets specs and prices side by side. AIsa names no harness, scored test cases, quality gate or quality scoring for the customer's agent.

SourceAIsa, aisa.one/docs llms-full.txt (Model Playground, model comparison)read 2026-09-25

Runbooks carry code checks, checklists and LLM judges that run in flight, and each run is scored against those checks with a verdict and a workload report. The customer evaluates its own agent's work with scored results across many runs. Judges and rubrics come with Squadron Platform.

SourceJetty, jetty.io homepage, docs/get-started and pricingread 2026-09-21

Scraping and crawling come from third parties such as Firecrawl, Tavily and Oxylabs, resold through the AIsa catalog. AIsa has no browser or computer control of its own.

SourceAIsa, aisa.one/docs llms-full.txt (Firecrawl, Tavily and Oxylabs API pages)read 2026-09-25

Jetty does not say whether a workload can operate a browser. Playwright and Firecrawl MCP servers are listed as ready on every run of the opencode runtime, but Jetty does not say whether that means a browser running inside its sandboxes.

SourceJetty, jetty.io/llms.txtread 2026-09-21