June 2026 Summaries

Arcade.dev and Nango are platforms designed for AI agent tool calling and API integrations, each serving different use cases. Arcade.dev is an MCP runtime focused on agent authorization, providing a large catalog of pre-built tools and handling per-user OAuth, but it is limited to tool calls without support for data syncs, webhooks, or coding-agent build loops. It is best suited for scenarios where tool calling is the entire scope. Nango, on the other hand, is a more comprehensive integration platform where coding agents like Claude Code and Cursor write integrations as code, covering tool calls, data syncs, webhooks, and unified APIs across over 800 APIs. It offers a scalable runtime with white-label authentication and deep observability, making it suitable for products where AI agents are integral and require extensive integration capabilities. Nango is recommended for engineers building API integrations for AI agents needing a broader range of functionalities beyond simple tool calls.

ID-JAG, or Identity Assertion JWT Authorization Grant, is an OAuth extension designed to streamline and enhance enterprise-level API integrations by shifting authorization control from individual users to an organization's identity provider (IdP), such as Okta. This approach eliminates the need for multiple user consents when accessing third-party APIs, enabling organizations to centrally manage which AI agents can interact with specific apps while maintaining security and visibility. ID-JAG operates by allowing the IdP to issue a scoped, short-lived token for an app's API, thus preventing the need for long-lived API keys and providing a more scalable solution for managing access. While ID-JAG represents a significant advancement in enterprise API management by allowing centralized control and revocation of agent access, its adoption is currently limited due to its reliance on OAuth and the requirement for each app to support the extension. Despite its potential to simplify and secure API interactions, ID-JAG is still in its early stages, with only a few applications and identity providers, such as Okta, implementing it, but its standard nature allows for potential broader adoption in the future.

Two-way data synchronization for customer-facing API integrations is a challenging process due to the need to manage conflicts, loops, deletes, and rate limits across different systems like Salesforce and HubSpot. Traditional "two-way sync" tools often cater to internal automations and fall short in meeting the demands of customer-facing products. The article evaluates multiple tools such as Nango, Merge, Paragon, and Workato, highlighting their strengths and limitations for two-way sync. Nango stands out as a code-first platform offering extensive control over data synchronization and conflict resolution, supported by coding agents that can dynamically build and maintain integrations across 800+ APIs. The complexity of two-way sync is rooted in independent system changes, making it essential to choose a platform that facilitates controlled, reliable, and scalable integration processes, particularly for businesses that require robust customer-facing solutions.

Coding agents excel at writing code but struggle with building robust API integrations, often relying on outdated training data and producing code that fails in production. To bridge this gap, API integration skills have been developed to guide agents in creating, testing, and deploying integrations by encoding procedural knowledge and providing a testing loop against real APIs. Notable skills include the Nango Function Builder skill, which works locally with multiple coding agents and offers a comprehensive approach for building and deploying integrations with managed auth, data syncs, and webhook ingestion. The Nango remote function builder allows for just-in-time integrations directly from a prompt without local projects, while Prismatic Skills focus on low-code workflows for Claude Code users. These skills are crucial for producing reliable, production-ready integrations, as they address the need for real API testing and deployment to a managed runtime, ensuring that integrations are functional and scalable.

The guide outlines the process of building a custom GitHub API integration using Nango and AI coding agents like Codex, enabling AI agents to perform actions such as creating issues, commenting on pull requests, and opening PRs on customer repositories. It discusses the differences between GitHub Apps and OAuth Apps, emphasizing the suitability of GitHub Apps for customer-facing products due to their fine-grained permissions and scalable rate limits. The integration process includes setting up a GitHub auth UI, establishing durable syncs for importing and updating issues and PRs, and implementing a signature-verified webhook handler to react to GitHub events in real time. Nango facilitates this by providing managed auth, retries, and observability across 800+ APIs, while Codex automates the writing and testing of integration logic. The guide also highlights the importance of combining scheduled syncs with real-time webhook responses for comprehensive data management and offers additional resources for exploring related API integrations.

Open-source API integration platforms are crucial for AI agents and SaaS products due to their transparency, lack of vendor lock-in, and extendable integrations. The text compares four such platforms: Nango, Composio, Arcade.dev, and Superglue, highlighting their open-source components, licensing, and functionalities. Nango offers a fully open-source platform under the Elastic License 2.0, allowing for self-hosting, credential management, and code ownership of integrations. In contrast, Composio and Arcade.dev have open SDKs but closed runtimes, with Composio's security incident in May 2026 exposing the risks of credential concentration in a closed cloud. Superglue provides an open-source runtime but limits its use in commercial products due to licensing restrictions. The importance of open-source platforms lies in the ability to audit credential storage, avoid vendor lock-in, and enable coding agents to build and extend integrations. Nango stands out as the most comprehensive open-source option, supporting a wide range of APIs and offering features like data syncs and webhooks, suitable for teams building AI agents or SaaS products.

The guide outlines a process for creating a custom Google Sheets API integration using Nango and AI coding agents like Codex, enabling users to link their spreadsheets to an application with a user-friendly OAuth interface. This integration allows for continuous synchronization of spreadsheet data, append operations, and report exports directly from the app or via AI agents. Key considerations include the need for OAuth 2.0 for accessing customer spreadsheets, managing API rate limits, and handling data formatting and range issues. Nango simplifies the integration by providing managed OAuth, retries, and observability, supporting over 800 APIs. The guide also details how AI agents can leverage the integration to interact with customer spreadsheets, highlighting Nango's ability to streamline API integration processes and facilitate dynamic, on-demand integrations.

API integration platforms are vital for AI agents and SaaS products to interface efficiently with customer tools like CRMs, Slack, and email systems, requiring platforms that manage authentication, credential storage, and execution. While managed cloud platforms are suitable for most, regulated industries and teams with strict data residency or security needs often prefer self-hosted solutions to keep credentials and execution on their infrastructure. Nango, Composio, Paragon, and Arcade.dev are notable platforms, each with unique offerings and limitations regarding self-hosting, open-source licenses, and enterprise requirements. Nango stands out with its open-source model and a free self-hosted edition that maintains customer credentials on user infrastructure, making it the preferred choice for teams needing full control over their data and integration processes. Each platform varies in its approach to hosting, integration building capabilities, and compliance standards, with Nango offering extensive customization and scalability for AI-driven integrations.

Nango is a code-first platform that enables customers to build API integrations with services like Salesforce and Slack, handling over 150 million functions monthly. Initially, customer code was run in a Node.js sandbox called vm2, but security vulnerabilities prompted Nango to isolate code execution through a dedicated runner model, later transitioning to AWS Lambda for improved resource management and observability. Lambda's hardware-virtualized microVMs offer stronger isolation, though challenges remain, particularly with tenant isolation since shared environments could pose security risks. To address this, Nango implemented per-customer Lambda functions, reducing the risk of cross-customer data exposure. Despite the increased rate of cold starts, this approach prioritizes security while maintaining functionality. The company is exploring further isolation enhancements, emphasizing the importance of a robust sandbox and resumable workloads to manage untrusted code securely.

The guide provides a comprehensive approach to building a custom integration with the Notion API using an AI coding agent, like Claude, and Nango, a code-first integration platform. It covers creating a Notion authentication UI for customers, setting up a durable sync to import and update Notion pages, and enabling the creation of pages and database entries from your app or AI agent. The guide highlights challenges such as understanding Notion's tree-like page structure, handling OAuth token rotation, and adhering to rate limits. It demonstrates how using Nango and AI agents can significantly reduce the integration time from weeks to about an hour by automating code generation and providing features like managed authentication, retries, and observability. The guide also includes instructions for setting up a test connection and deploying the integration, with the complete demo available on GitHub.

Building email and calendar API integrations involves managing OAuth, incremental syncs, and push notifications across providers like Google, Microsoft, and IMAP, highlighting the complexity of integrating these services. The text discusses various platforms for mail and calendar integrations in 2026, evaluating them based on provider coverage, integration building support, API accessibility, authentication ownership, and additional integration capabilities beyond mail and calendar. Nango is highlighted as a versatile platform enabling coding agents to build integrations with full API access, while Nylas offers a unified API for communications data but with limitations. Aurinko provides a pass-through option with minimal data storage, and Unipile focuses on messaging channels like LinkedIn and WhatsApp, with added email and calendar support. The text emphasizes the preference for platforms like Nango, which offer broader integration capabilities and coding agent support, making them suitable for teams expecting to expand beyond basic communications APIs.