IonBin
All pages
Search

Relevance AI

AI agent platform
OpsSales Agent platform MCPAPI/CLIFile import

Independent review. Unpaid; no partnership with Relevance AI. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Platform for building AI agents and multi-agent workforces for sales, research and operations. Its free MCP server lets client apps such as Claude, ChatGPT and Cursor build and run agents; usage is billed to your plan.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
Platform for building AI agents and multi-agent workforces for sales, research and operations. Its free MCP server lets client apps such as Claude, ChatGPT and Cursor build and run agents; usage is billed to your plan.
Differentiation
Documented fit: Ops teams prototyping AI workers with human checkpoints. Uniqueness is not established.
Replaceability and switching
Compare Lindy, n8n. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: One-off chat tasks. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Best for
  • Ops teams prototyping AI workers with human checkpoints
Not for
  • One-off chat tasks

Top use cases

  • Build and manage agents from an MCP client source ↗
  • Trigger agents and tools from code with the SDK source ↗

In depth

Plans

Pro is $19/month with annual billing or $29 monthly; Team is $234 with annual billing or $349 monthly. Pro includes 2,500 Actions and $20 Vendor Credits per month; Team includes 7,000 and $70. These are organization-shared allowances. Vendor Credits carry forward while subscribed; base Actions reset at renewal. Free is retired. Extra Actions and model usage can add cost. source ↗

MCP scope and longer runs

Connections authenticate to a specific project. Viewer and Chat roles restrict tool access; higher roles can choose Run-Only mode. The server itself has no separate fee, but execution uses the paid plan. Synchronous agent calls time out after 120 seconds; longer work uses asynchronous execution and polling. source ↗

Knowledge and API access

Knowledge uploads include CSV, PDF, Excel, JSON and audio. Review extracted content before relying on it. SDK access uses a Relevance API key; key creation requires Editor or higher, with an additional Enterprise Member allowance. source ↗

How to use it with AI

How Relevance AI connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented Relevance AI has an official MCP server and Claude (incl. Claude Code) supports MCP, but Relevance AI's docs don't name this pairing. Auth setup may differ. Relevance AI MCP docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Relevance AI publishes an API, but this pairing still needs network, authentication and execution-scope checks. Relevance AI API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Relevance AI is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Relevance AI's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Relevance AI file docs ↗Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented Relevance AI has an official MCP server and OpenAI Codex supports MCP, but Relevance AI's docs don't name this pairing. Auth setup may differ. Relevance AI MCP docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Relevance AI publishes an API, but this pairing still needs network, authentication and execution-scope checks. Relevance AI API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Relevance AI is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Relevance AI's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Relevance AI file docs ↗OpenAI Codex file docs ↗
Google Antigravity Not documented Relevance AI has an official MCP server and Google Antigravity supports MCP, but Relevance AI's docs don't name this pairing. Auth setup may differ. Relevance AI MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks Relevance AI publishes an API, but this pairing still needs network, authentication and execution-scope checks. Relevance AI API ↗Google Antigravity docs ↗ Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Relevance AI is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Relevance AI's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Relevance AI file docs ↗Google Antigravity file docs ↗

Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.

Agent compatibility

Agent platform MCPAPI/CLIFile import
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗
API / CLIYes Official docs ↗
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importYes Official docs ↗

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

As an agent platform

MCP client support to verify.

Workflows using this tool

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

Lindy

AI assistant

AI teammate for inbox, calendar, research and repeatable work. It can use compatible hosted MCP tools and maintain files in personal or team memory. Review enabled actions and approval settings before delegating work with external effects.

Agent platform BrowserFile import
Ops

n8n

Workflow automation

Workflow automation with a no-license-fee self-hosted Community Edition and paid Cloud plans. The MCP Server Trigger exposes connected tools and workflows to MCP clients. Self-hosting still requires infrastructure, maintenance and compliance with n8n's license.

Automation hub MCPAPI/CLIFile import
Data