All Swytchcode Engineering blogs
A scheduling agent that checks availability and then books the slot has a gap between those two steps — and a retry can fall straight into it. Here's how Swytchcode closes that gap.
A retried "create" call doesn't update an existing contact, ticket, or row — it makes a second one. Here's why that happens across CRMs, databases, and ticketing tools, and how Swytchcode prevents it.
Most email APIs have no idempotency key to catch a repeat send, which makes a duplicate email a harder problem than a duplicate charge. Here's how Swytchcode handles the gap.
A timed-out payment call and a retry loop is all it takes for an agent to charge someone twice. Here's why that happens and how Swytchcode's per-call idempotency and approval policies stop it.
Not every failed API call should be retried, and not every retry should happen the same way. Here's what a retry policy actually decides, in plain English, and how Swytchcode configures one per API.
An idempotent API call does the same thing no matter how many times you make it. Here's what that means in plain English, why AI agents need it more than people do, and how Swytchcode handles it.
Circle's API moves stablecoin value, and a retry that generates a new idempotency key looks like a brand new transfer to Circle. Here's how Swytchcode keeps that key consistent across retries and backs transfers with policy instead of trust.
GDELT's news-search API needs no key, but it still rate-limits, and its defaults are shaped for a browser, not a model. Here's how to shape one query that fits in an agent and respect the pacing rule, until GDELT has a governed Swytchcode bundle.
Bitbucket's app passwords and API tokens authenticate with different usernames, and mixing them up is what causes a silent 401. Here's how Swytchcode handles the credential pairing and gates write access behind policy.
Twilio's Messages create has no idempotency key, so a retried send is a second, separately billed text. Here's how Swytchcode stores the SID from every attempt and blocks a second send in policy before it ever reaches Twilio.
A Telegram bot token sends as the bot, and the platform refuses to let it message someone who hasn't opened the chat first. Here's how Swytchcode restricts sends to chats the bot has actually seen, keeps the token out of the prompt, and backs bursts of messages with policy.
Figma's API doesn't separate reading a design from changing one. Here's how Swytchcode lets you connect an AI agent to Figma without handing it more access than the job needs.
A Revolut counterparty in state created is not a paid transfer, and payment drafts wait for approval in the Business app. Here's how Swytchcode keeps an agent on draft-only access until that approval habit is proven, and backs retries with the same request id.
A PayPal refund reverses one capture; a payout sends brand-new money, and an agent can confuse the two. Here's how Swytchcode keeps them on separate allowlist entries and backs retries with the same request ID instead of trust.
Set a call baseline for each method, then compare it the morning after a prompt edit. A flat total can hide a shift from a read method to a write method.
A provider count hides the real maintenance work. Twelve enabled methods on one host need more policy and review than six hosts that each expose one read.
Security sends the agent back when the doc names a vendor and skips the methods. Copy this field list into the repo and fill every method ID from the CLI.
The agent stalls on the internal service nobody documented. Search the public registry for known providers, then build the other rows from your own call logs.
Time a clean machine from install through a passing dry run, and write down each command. Publish the log you measured, with the provider and CLI version.
Start the agent on reads the user could already open. Add one reversible write after a quiet week. Hold refunds, deletes, and identity changes for a person.
Stage the agent by enabling one method at a time, reads before writes. Report enabled methods over scoped methods, and read the log before the next write.
Validate the policy file on every commit, and dry-run each method the diff added. Keep a live provider call out of the pipeline until after the merge.
Why teams look past Tray.ai when an agent's permissions change in a dashboard, and how Workato, Boomi, MuleSoft, Informatica, Celigo, n8n, Make, Zapier MCP, Pipedream, and Swytchcode differ. Prices checked November 2026.
An HR agent can write an offer or send a rejection on its own. Compare five tools on candidate PII, blocked writes, and who must approve the change.
Why teams look past Kong in 2026, and how Apigee, AWS API Gateway, Azure API Management, Tyk, Traefik Hub, Zuplo, MuleSoft, Workato, Boomi, and Swytchcode differ. Prices checked November 2026.
Why teams look past Workato in 2026, and how Boomi, MuleSoft, Tray.ai, Informatica, Celigo, n8n, Make, Zapier MCP, Pipedream, and Swytchcode differ. Prices checked November 2026.
Why teams look past Apigee in 2026, and how Kong, AWS API Gateway, Azure API Management, Tyk, Traefik Hub, Zuplo, MuleSoft, Workato, Boomi, and Swytchcode differ. Prices checked November 2026.
Why teams look past MuleSoft in 2026, and how Workato, Boomi, Informatica, Kong, Apigee, AWS API Gateway, Azure API Management, Tyk, Zuplo, and Swytchcode differ. Prices checked November 2026.
Why teams look past Temporal in 2026, how Restate, Inngest, Trigger.dev, DBOS, Hatchet, Step Functions, Windmill, QStash, and Celery differ, and where Swytchcode fits under the workflow. Prices checked November 2026.
Why teams look past Boomi when agents make calls no process map covers, and how Workato, MuleSoft, Tray.ai, Informatica, Celigo, n8n, Make, Zapier MCP, Pipedream, and Swytchcode differ. Prices checked November 2026.
Why teams look past Inngest in 2026, how Trigger.dev, Temporal, Restate, Hatchet, DBOS, QStash, Step Functions, Windmill, and Celery differ, and where Swytchcode fits inside a step. Prices checked November 2026.
Merge's Common Model can drop provider-specific fields your agent needs. Ten alternatives compared on how they reach those fields, with prices checked November 2026, and where Swytchcode governs the direct call.
Why teams look past Trigger.dev in 2026, how Inngest, Hatchet, Temporal, Restate, DBOS, Windmill, Step Functions, QStash, and Celery differ, and where Swytchcode fits inside a task. Prices checked November 2026.
Apideck's unified spec does not carry every provider field, and some writes are silently ignored. Ten alternatives compared on field access, write safety, and price, checked November 2026.
Hookdeck retries and replays inbound webhooks, but a replay is a new event and dedupe is best effort. Ten alternatives compared, with prices checked November 2026, and where Swytchcode governs the agent's next call.
Why teams look past Svix in 2026, and how Hookdeck Outpost, Convoy, Hook0, EventBridge, SNS, Knock, Novu, Courier, Zapier, and Swytchcode differ. Prices checked November 2026.
Why teams look past WorkOS in 2026, and how Auth0, Okta, Clerk, Stytch, Frontegg, Descope, Entra ID, FusionAuth, Keycloak, and Swytchcode differ. Prices checked November 2026.
Why teams look past Auth0 in 2026, and how WorkOS, Okta, Clerk, Stytch, Frontegg, Descope, Entra ID, FusionAuth, Keycloak, and Swytchcode differ. Prices checked November 2026.
A personal access token gives your agent your permissions across every project you can see. A project access token gives it one project. That choice is the whole security model.
Cancelling a workflow takes a workflow ID and nothing else. There is no project in the path, so an agent can stop a colleague's release deploy with one call.
Fireworks lets your agent call a second model as a tool, which means a model, not your code, is deciding how many tokens get spent. How to cap that spend with an allowlist and policy instead of trust.
Someone renames a field in the Airtable UI and your agent breaks with an error saying the field does not exist, while you are looking right at it. How Swytchcode keeps delete off the allowlist while that schema drifts.
"The Hugging Face API" is really three APIs sharing one token, and the write one is almost never what an agent needs. How to scope the credential and the allowlist so a confused tool call can't reach it.
Building an MCP server gives you exactly the surface you design. Buying an execution layer gives you that surface plus the governance layer most teams end up needing anyway.
Video generation takes minutes, there are no webhooks, and agents are terrible at waiting. How to run long jobs on the Luma API without burning tokens or paying twice.
An agent's call log is not the same as knowing what the agent decided and why. The audit trail you need captures decisions, not just requests.
A version bump that breaks a human developer surfaces in minutes. One that breaks an agent running unattended can run silently for days before anyone notices.
Who owns the idempotency key, and does a retry actually reuse it? Temporal, Inngest, Trigger.dev, AWS Step Functions and Cloudflare Workflows compared.
Duplicate delivery firing the same agent twice is the failure mode webhook infrastructure rarely documents. Hookdeck, Svix, Convoy and Zapier Webhooks compared.
Rotation mid-run, and whether the secret ever enters the model's context: what to look for in a secrets manager when the caller is an agent, not a human developer.
What an idempotency key actually promises, how to generate and scope one, and what providers guarantee when a retry is already in flight.
Log the call where it is sent, not where it is described. Record the operation, the actor, the idempotency key, the policy decision and the outcome. Never record the credential. If the agent writes its own log, the calls that were blocked quietly disappear.
Multi-tenant OAuth means one stored grant per customer, not one token in a .env file. If every customer connects their own Slack or GitHub, you need a hosted connect flow, a credential stored against their ID, and every call tagged with whose account it used. Here is who does what.
Coding agents are good at running shell commands and bad at inventing API parameters. A CLI between the agent and the API fixes both: the agent names the operation, the command attaches the credential, checks the arguments, applies your rules and retries safely.
Grok's custom connector takes an MCP server URL and discovers whatever tools it exposes. That is a real door into Grok, and it comes with one requirement the docs state plainly: your server has to be reachable over the public internet.
The 2026-07-28 revision removed sessions, the initialize handshake, ping, and SSE stream resumability. Here is every change that affects a server you already run, what to do about each one, and the six patterns worth adopting.
Connecting an assistant to your inbox, drive or CRM is a permission decision, not an integration decision. Twelve checks, in the order a security review actually asks them, and the one assumption that causes most of the damage.
A triage bot that labels issues instead of commenting on them, built on verified canonical method IDs. Includes the GitHub API quirk that makes every pull request look like an issue, and why that breaks naive triage.
You do not need an MCP server per provider. One server, seven tools and an allow list reach every API in the catalog, from Cursor, Claude Code, Windsurf, Copilot, Codex, Gemini CLI and more. Here is the setup for each.
MCP is a standard way for an AI model to discover and call tools that live outside it. It replaced a world where every assistant invented its own plugin format. Here is what it is, what it is not, and what it leaves you to solve.
Claude Code already has a shell, which changes the calculus. Half of what people install MCP servers for, it can do with a command. Here is what is genuinely worth adding, and the one job where MCP earns its place.
The useful question is not which MCP servers exist, it is which jobs you actually need one for inside Cursor. There are five, and the one most people get wrong is letting the agent call real third-party APIs.
An empty 400 is the worst failure an AI agent can hit, because the model cannot tell a wrong field name from a wrong value and will happily retry the same broken call forever. Here is how to read one, and how to stop generating them.
TypeSafe doesn't ship an MCP server for Jev. What exists is Swytchcode's MCP server, which exposes Jev alongside every other integration as tools your coding agent can call. Here is the setup for Claude Code, Cursor, Codex and anything else that speaks MCP.
An assistant that can look up an order is helpful. An assistant that creates or changes the order can ship the same goods twice if a retry is treated as a new order.
Free tiers stop in different places. This article puts Composio, Arcade, Nango, Zapier MCP, Pipedream, and Swytchcode on one table and explains what each number actually counts.
Open source gives you the code. It does not run the login, the retry, or the upgrades. This article says what each license lets you do, and what you still operate.
Fifty API logos is a slide. The work is how many actions can create or change a record. This article compares catalogs, unified APIs, and one-action runtimes on that count.
An internal assistant is a good first agent. It is not low-risk if it signs in as an admin. This article compares suite tools, catalogs, iPaaS, and Swytchcode by the scope of that login.
A payment agent is safe only if a retry is the same charge. This article compares Stripe, catalogs, and Swytchcode by who creates the idempotency key and whether the second try reuses it.
A small team can connect an assistant without hiring people to build login, retry, and logs. This article names what you still decide, and what each tool costs in October 2026.
An assistant that can tell you the balance is helpful. An assistant that can send the payment is a different system. Here is the difference, in plain language, and the finance tools we already connect.
If an email send times out, clicking send again is safe on some providers and a second email on others. Here is what each provider's docs said in October 2026.
Connecting Claude and connecting your other tools are two different logins. Here is where each one should live if you are setting this up for the first time.
Enterprise API management governs the APIs you publish. Agents mostly call APIs someone else published. That outbound gap is not an API gateway feature.
API observability shows the HTTP call. Agent traffic also has a tool choice and a set of calls that were refused before any request was sent. Most tools show one of those, not both.
Temporal, Inngest, and Restate replay the workflow. Replaying the workflow is not the same as a safe retry of the provider call inside it.
A unified API gives one schema for many providers. The fields that schema left out are the ones your customer actually uses. Here is when that trade-off is worth it.
An MCP gateway decides which tool a caller may invoke. An execution layer decides how that call becomes an API request. The allow list is not the same at those two hops.
PreToolUse fires before the tool function, which is before the HTTP call. It can block a repeat it can see. It cannot tell you the server already committed.
AI can generate API tests from a schema you hand it. It cannot invent the contract, grade itself against that invention, and call the result coverage.
The Agent SDK runs a tool at least once. Exactly-once is a property of the API that stores the idempotency key, and the key has to be the same on the retry.
Roo Code asked for a tool call and got an assistant message with none. The loop stalls because the model talked, or because the tool schema was not something it could fill.
The MCP 2026-07-28 spec removed session state from the protocol, which is the right call for scaling but leaves retry safety completely unaddressed. We walk through the duplicate-refund failure, the three places an idempotency key can actually live, and the trade-offs of each.