ramp
Start here
| Question | Answer |
|---|---|
| Best for | Finance agents that inspect cards, transactions, reimbursements, approvals, trips, and policy answers. |
| Connect with | MCP tools from archal clone start ramp. |
| Known limits | Architecture Preview: Ramp is MCP-first and fixture-scoped with seeded state overlays. It does not expose a general REST fidelity surface or ledger-accurate finance simulator. |
| Seeds | Common seeds: default, empty, ramp-receipt-mismatch, ramp-expense-split. See Seeds for usage. |
What it covers
The Ramp clone mirrors Ramp’s published agent-facing MCP tools within the checked-in fixture corpus for:- Cards and card controls
- Funds and one-time agent card credentials
- Transactions, receipts, memos, and missing-item workflows
- Bills, reimbursements, purchase orders, and approval queues
- Users, org charts, travel bookings, trips, and locations
- Policy and help-center question answering
Seed model
The current Ramp clone ships with:defaultfor a finance-manager style workspace with cards, approvals, and travelemptyfor blank-state generation and harness flows
Surface
Ramp is MCP-first today. There is no general REST fidelity surface, and fixture-backed parity should not be treated as full Ramp or finance-system behavior. Use the MCP URL printed byarchal clone start ramp, or let archal run handle it through
.archal.json. See the clones compatibility matrix.