Independent review. Unpaid; no partnership with Ramp. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Corporate cards, expenses and bill pay with spend controls. Its MCP server lets assistants query spend and act on supported approvals, reimbursements and cards within user permissions. A separate developer API is documented.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Corporate cards, expenses and bill pay with spend controls. Its MCP server lets assistants query spend and act on supported approvals, reimbursements and cards within user permissions. A separate developer API is documented.
Differentiation
Documented fit: Finance teams enforcing spend policy. Uniqueness is not established.
Replaceability and switching
Compare Mercury. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Sole proprietors. 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.
IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.
AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.
Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.
Best for
Finance teams enforcing spend policy
Not for
Sole proprietors
Top use cases
Pull card transactions and spend data through the API source ↗
Query spend and approve or reject transactions and reimbursements from an AI assistant source ↗
In depth
Plans
Ramp's base plan is $0 per user/month (cards, expenses, bill pay). Plus is $15 per user/month plus a platform fee based on team size, with 20% off for annual billing. Enterprise is custom. Checked 2026-10-18. source ↗
MCP boundaries
Permissions follow the signed-in user; company-wide tools generally require admin access. Bill approvals and receipt-file uploads are unavailable over MCP. Use Ramp directly for those. Hosted custom-client redirect URLs require allowlisting. Ramp now recommends its CLI for coding agents such as Cursor. source ↗
Invoice input
Bill Pay accepts CSV/XLSX spreadsheets and supported invoice files. Drag-and-drop accepts up to ten documents at a time, up to 50 MB each. Eligible complete CSV drafts can submit automatically when automatic bill submission is enabled; review that setting before importing. source ↗
How to use it with AI
How Ramp connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedVerify which side exports and which imports, supported formats and permissions. Ramp'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.Ramp file docs ↗Claude (incl. Claude Code) file docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Ramp publishes an API, but this pairing still needs network, authentication and execution-scope checks.Ramp API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Ramp is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Ramp's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.Ramp file docs ↗OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Ramp is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Ramp's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Ramp 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.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Business banking for startups. Mercury MCP (in beta) connects AI tools over OAuth to read accounts and transactions and to request payments or transfers, which still need approval in Mercury; an API is also documented.