IonBin
All pages
Search

Apex

Docs and knowledge
ContextSalesOps Browser

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

A hosted “business memory” that reads your connected tools into one graph of people, deals and commitments and serves it to AI assistants over MCP. Waitlist only, no public pricing. A context layer beside Ion’s top picks, Notion and Obsidian. Vendor pages checked, not tested.

The Ion perspective

The five-point review

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

Value
A hosted “business memory” that reads your connected tools into one graph of people, deals and commitments and serves it to AI assistants over MCP. Waitlist only, no public pricing. A context layer beside Ion’s top picks, Notion and Obsidian. Vendor pages checked, not tested.
Differentiation
Documented fit: Owner-operators whose context is spread across email, calendar, CRM, chat and books; People who switch between AI assistants and want each one to start from the same business context; Delegating scoped read access to an assistant or bookkeeper without sharing whole accounts. Uniqueness is not established.
Replaceability and switching
Compare Notion, Obsidian. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Writing and organizing notes yourself (use Notion or Obsidian); Context that must stay as files on your own device; Buyers who need published pricing, a named contracting entity or lawyer-reviewed terms today. 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
  • Owner-operators whose context is spread across email, calendar, CRM, chat and books
  • People who switch between AI assistants and want each one to start from the same business context
  • Delegating scoped read access to an assistant or bookkeeper without sharing whole accounts
Not for
  • Writing and organizing notes yourself (use Notion or Obsidian)
  • Context that must stay as files on your own device
  • Buyers who need published pricing, a named contracting entity or lawyer-reviewed terms today

Top use cases

  • Ask an assistant who someone is and where things stand, answered from your connected mail, calendar and CRM source ↗
  • List what you promised and who is waiting on you source ↗
  • Hand a project from one AI assistant to another with the history of what passed between them source ↗
  • Act in a connected tool (send, post, update a record) with every action logged source ↗

In depth

What it is

Apex describes itself as your business memory: you sign in once per tool (email, calendar, chat, CRM, books, files), grant read access and choose what each can see, and it builds one graph of people, companies, meetings, messages, deals, commitments and projects. Nothing is installed locally. The vendor lists 1,379 connectable tools. source ↗

How assistants use it

Assistants read the graph over MCP and can act back in the connected tools. The documented tools include searching the graph, open commitments, a person lookup, reading a note with its evidence, recent knowledge, running an action, an activity log, project sync and hand-off between assistants. Every action is recorded, including failures, and answers name their sources. source ↗

Access, hosting and terms

Access is by waitlist, and businesses over US$400K are offered a call. The privacy notice says the product runs on Vercel, waitlist answers sit in Supabase-hosted Postgres and payments go through Stripe. The terms name the operator only as Apex, call it early software offered as-is, and say both documents have not yet been reviewed by a lawyer. source ↗

Check which product you are joining

Older documentation pages elsewhere on the same domain describe a different design: a self-hosted, MIT-licensed autonomous agent in private beta. The current homepage, docs, terms and privacy notice (updated 20 September 2026) describe the hosted memory service above. Confirm hosting, data location and licensing with the vendor before connecting accounts. source ↗

Compared with Notion and Obsidian

Notion and Obsidian are Ion’s top picks because you write and organize the context yourself, in a shared workspace or as Markdown files you own. Apex is a secondary, different approach: it assembles context automatically from the tools you already use and serves it to assistants. Keep deliberate notes, SOPs and decisions in Notion or Obsidian; consider Apex once it is generally available and priced. source ↗

How to use it with AI

How Apex 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 Vendor docs: reads the same graph over MCP. Waitlist product; not tested by IonBin. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Apex named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Public API unconfirmed Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Apex 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. Apex's recorded upload/import status is to-verify; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented https://apex.host/vega/docs lists the MCP tools (search_brain, open_commitments, who_is, read_note, apex_run and others). Access is by waitlist, so IonBin has not connected to it. Not documented Public API unconfirmed Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Apex 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. Apex's recorded upload/import status is to-verify; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. OpenAI Codex file docs ↗
Google Antigravity Not documented https://apex.host/vega/docs lists the MCP tools (search_brain, open_commitments, who_is, read_note, apex_run and others). Access is by waitlist, so IonBin has not connected to it. Not documented Public API unconfirmed 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. Apex 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. Apex's recorded upload/import status is to-verify; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Google Antigravity file docs ↗

Apex's docs also name: ChatGPT.

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 21, 2026.

To verify Pricing and plan limits · Legal entity named in the terms · Data export and deletion workflow beyond an email request

Agent compatibility

Browser MCP?API/CLI?File import?
LevelStatusDetail / source
Native connector / MCPTo verify Official docs ↗ lists the MCP tools (search_brain, open_commitments, who_is, read_note, apex_run and others). Access is by waitlist, so IonBin has not connected to it.
API / CLITo verify The docs say anything with an API or MCP server can be connected as a source; a public Apex API is not documented.
Browser / manualYes Browser access recorded; no confirmed MCP server or API in this listing.
File upload / importTo verify It reads connected tools rather than importing files; per-tool read access is chosen at connection (https://apex.host/vega/docs).

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

Appears in these proposed stacks

Connection capabilities to compare

No confirmed MCP server yet.

Explained in the wiki

Review

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

Alternatives

Notion

Docs and knowledge

Ion’s top pick for notes, meeting transcription and shared context: pages, databases and AI Meeting Notes in one workspace. Business adds Notion Agent and meeting notes; a hosted MCP server lets AI clients read and update pages.

MCPAPI/CLIFile import
Used by Ion — Used by Ion. The creator currently prefers Notion for note-taking; this is a personal use signal, not a universal ranking. SOPs

Obsidian

Docs and knowledge

Ion’s top pick when notes and agent context should be plain Markdown files you own: a local vault with links, plugins and an official CLI. Sync and Publish are optional paid add-ons.

API/CLIFile import
Local