Get to know Cadenya
We’re developers who love to build. We set out to create a yes-code platform that makes building agents feel like the best parts of building software.
Five products host an AI agent for you in 2026, and they split into two kinds. Three run their own agent loop and you configure it: Claude Managed Agents, OpenAI’s Agents API, and Cadenya. Two run the loop you write: LangSmith Deployment and Amazon Bedrock AgentCore.
After that, a few facts decide most picks: which models you can use, how a human-in-the-loop approval works, whether a dropped stream can resume, how your API becomes tools, and what you pay for.
Every figure below comes from the vendors’ own docs and pricing pages, checked on September 28, 2026.
The short version
- Claude Managed Agents if you want Claude with a sandbox per session and approvals set as a permission policy.
- LangSmith Deployment if you write the agent yourself (LangGraph or another framework) and want it hosted in the US or the EU.
- Amazon Bedrock AgentCore if you write the agent, need any model on AWS, and need HIPAA eligibility or FedRAMP.
- OpenAI’s Agents API if you want OpenAI’s managed harness and OpenAI models.
- Cadenya if your agent’s tools are your own API, you want any model with nothing to run (what it offers).
Pricing, models, and who writes the loop
| Claude Managed Agents | LangSmith Deployment | Amazon Bedrock AgentCore | OpenAI Agents API | Cadenya | |
|---|---|---|---|---|---|
| Who writes the loop | Anthropic’s harness | You | You | OpenAI’s Codex harness | Cadenya, configured by you |
| Models | Claude 4.5 and later | Whatever your code calls | Any: Bedrock, OpenAI, Gemini, Claude, and more | OpenAI models | Any provider you connect, set per variation |
| Price | $0.08 per session-hour while running, plus tokens | Plus: $39 a seat a month, plus $0.0675 per vCPU-hour of runtime | $0.0895 to $0.1276 per vCPU-hour, plus memory, billed per second | Model tokens, tools, and $0.03 per 20 minutes for a 1 GB sandbox | $0 for 1,000 loops a month, $49 for 50,000 |
Human-in-the-loop approvals, streaming, and tools
| Claude Managed Agents | LangSmith Deployment | Amazon Bedrock AgentCore | OpenAI Agents API | Cadenya | |
|---|---|---|---|---|---|
| Human approval | always_ask, answered with a user.tool_confirmation event | LangGraph interrupt() | A harness hook that calls a Lambda function | None in the API (the Agents SDK has one) | Tool approvals, answered from the API, a webhook, Slack, or the React widget |
| Streaming after a dropped connection | Not stated | Resumes from the last event ID, and join_stream attaches to a running thread | Not stated | Streams “do not replay missed events” | Resumes from the last event ID, and the TypeScript SDK reconnects on its own |
| Your API as tools | MCP (up to 20 servers) and custom tools | Your code | Gateway turns OpenAPI, Smithy, and Lambda into MCP tools | MCP and function tools | OpenAPI 3 (checked hourly), MCP, HTTP, and Bare tools |
| Code the model writes | A container per session: bash, files, web | LangSmith Sandboxes | Code Interpreter: Python, JavaScript, TypeScript | A hosted sandbox or your own executor | Pairs with a sandbox such as E2B through a tool |
Claude Managed Agents
Anthropic’s “pre-built, configurable agent harness that runs in managed infrastructure.” Each session gets a sandbox where Claude can run bash, read and write files, and search the web, and you pay $0.08 per session-hour only while the session is running, plus tokens at the usual rates (Claude Sonnet 5 is $2 and $10 per million input and output tokens). Time spent idle, waiting for you or for a tool confirmation, is free.
Human-in-the-loop approvals are a permission policy. Set a tool to always_ask and the session pauses for a response, which you send as a user.tool_confirmation event. It connects up to 20 MCP servers.
Two things set it apart from the others. It’s Claude only, and there’s no OpenAPI import, so your API reaches it as MCP or as custom tools you execute. Pick it when the agent should do things in a sandbox and Claude is the model you want.
LangSmith Deployment
LangChain’s “workflow orchestration runtime purpose-built for agent workloads,” formerly LangGraph Platform. You write the agent, in LangGraph or, through a wrapper, the Claude Agent SDK, Strands, CrewAI, AutoGen, or Google ADK, and its Agent Server hosts it. Deployments live in the US or the EU.
Pricing mixes seats and metering. Plus is $39 a seat a month, includes one free Serverless (Small) deployment, and bills runtime at $0.0675 per vCPU-hour and $0.009 per GiB-hour, with databases for Dedicated deployments on top. Self-hosting is “an add-on to the Enterprise plan” with a license key, and it brings ClickHouse, Postgres, Redis, and Kubernetes with it.
Approvals are LangGraph interrupts. Streams are resumable: “if a connection drops, reconnect with the last event ID to pick up where you left off.” One catch from the same docs: a resumed node runs again “from the beginning”. Pick it when you want to own the agent’s code and have someone else run it. LangSmith Deployment pricing and alternatives goes deeper.
Amazon Bedrock AgentCore
AWS’s “agentic platform for building, deploying, and operating highly effective agents securely at scale using any framework and foundation model.” It’s a set of parts: Runtime (your agent in its own microVM per session), Memory, Gateway, Identity, Code Interpreter, Browser, and Observability. It runs CrewAI, LangGraph, LlamaIndex, Google ADK, the OpenAI Agents SDK, and Strands, with any model.
Runtime bills per second of real use: $0.0895 per vCPU-hour and $0.00945 per GB-hour on v1 microVMs, with “no upfront commitments or minimum fees.” AWS’s own worked example, a support agent with 1 million sessions a month, comes to $6,703. The compliance list is the longest here: HIPAA eligible, FedRAMP, SOC 2, and seven ISO standards.
You write and deploy the agent code yourself, and you add the parts you need. The built-in approval point is a hook that calls a Lambda function. Pick it when you’re on AWS and you write the agent. AgentCore alternatives covers the options.
OpenAI’s Agents API, and the rest of AgentKit
OpenAI’s agent pieces ship separately. The Agents API “gives your application access to the Codex harness through an OpenAI-managed API”, with sessions, compaction, and recovery. The Agents SDK runs the loop in your own app instead. ChatKit is an embeddable chat UI (the pricing page files its storage under “Agent Kit”). And Agent Builder, the visual canvas, “is scheduled to shut down on November 30, 2026.”
The Agents API bills model tokens, tools, and sandboxes: $0.03 per 20 minutes for a 1 GB container, by the minute after a 5-minute minimum. Its streams “do not replay missed events”, and it has no approval step of its own (the Agents SDK has one). Pick it when you want OpenAI’s harness and OpenAI models, managed.
How to choose
Answer four questions in order:
- Does the agent need more than one model vendor? That rules out Claude Managed Agents and the Agents API.
- Do you want to write and host the agent loop yourself? LangSmith Deployment and AgentCore run the code you write. Cadenya runs the loop for you, on any model.
- Are the agent’s tools your own API? Cadenya turns an OpenAPI document into tools and re-checks it each hour. AgentCore needs Gateway, and the others take MCP servers or tools your code runs.
- Does the agent run code it writes? Managed Agents, AgentCore, and the Agents API include a sandbox. LangSmith offers LangSmith Sandboxes, and Cadenya pairs with one.
What does Cadenya offer that the other four don’t?
Claude Managed Agents and OpenAI’s Agents API run the loop, on their own models. LangSmith Deployment and AgentCore run any model, and you write the loop. Cadenya runs the loop for you, on any model, with your own API as the tools. Here’s what that covers:
- Any model, with no vendor tie. Managed Agents runs Claude, and the Agents API runs OpenAI models. On Cadenya, the model is a setting on a variation: any model on OpenRouter or your own endpoint that speaks the OpenAI chat format, on your own keys. Weighted variations route more traffic to whichever model or prompt users rate higher.
- The loop, already written, with nothing else to run. LangSmith Deployment and AgentCore host the agent you write. On Cadenya you set the prompt, model, tools, and approvals on a variation, and Cadenya calls the model, runs the tools, streams each reply, and compacts the context window. There’s no agent code to deploy and no self-hosted runtime to size.
- Built for product agents, not coding agents. Managed Agents gives Claude a shell and a container, and the Agents API runs the Codex harness. A Cadenya agent works through your product’s API, sits in your app as a chat widget, and acts as the signed-in user.
- Your OpenAPI document as the tools. A tool set turns every operation in an OpenAPI 3 document into a tool, re-checks the document each hour, filters the list, and loads tools on demand, so a big API doesn’t fill the context window. Managed Agents and the Agents API take MCP servers or tools your own code runs, and AgentCore needs Gateway, at $0.005 per 1,000 calls.
- Human-in-the-loop approvals, screen included. Mark a tool as needing approval and the objective pauses on
toolApprovalRequested, and the answer can come from your backend, a webhook handler that posts to Slack, or a person in the React chat widget. A denial can carry a memo that steers the agent. The Agents API has no approval step of its own. - Acting on behalf of the signed-in user. Your backend mints a widget session per user, and it can carry that user’s short-lived token as a secret that overrides the shared API credential, so your API sees the user’s own token on each tool call. AgentCore leaves that to you: “your client backend should maintain the relationship between users and their session IDs.”
- Resumable streaming. The event stream honors
Last-Event-ID, and the TypeScript SDK reconnects on its own. The Agents API’s streams “do not replay missed events.” - Durable state that outlives your deploys. Every objective keeps a durable event log on Cadenya that you can list, stream, or receive as signed webhooks. An objective also keeps its variation’s snapshot, so editing the agent never changes a conversation that’s already running.
- Versioned SDKs in four languages. Cadenya’s TypeScript and Python SDKs reached 1.0 on August 15, 2026, and all four SDKs (TypeScript on Node 18, Python 3.9, Ruby 3.1, and Go 1.22) shipped 1.9.0 on October 28, under Apache-2.0. The TypeScript SDK has shipped 113 versions since April 2026.
- A price per model call, not per hour. Free for 1,000 loops a month, $49 for 50,000, then $0.0015 a loop, where a loop is one LLM request. There are no seats, session-hours, or vCPU-hours to estimate.
The tool sets guide shows how your API becomes an agent’s tools, and the free plan needs no card.
No account yet? A coding agent can create a temporary workspace with cadenya workspaces create --temporary, run its first objectives there, and hand you a link to claim it, as auth.md explains. To create an account, sign up at app.cadenya.com/signup, then copy your API key from the API keys page at app.cadenya.com/account/apiKeys.
Grow wherever AI goes next.
Start shipping agents that are equipped to evolve.