Skip to main content

​
What it covers

The Ramp twin mirrors Ramp’s published agent-facing MCP tools 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 twin ships with:
  • default for a finance-manager style workspace with cards, approvals, and travel
  • empty for blank-state generation and harness flows

​
Notes

This twin is modeled from Ramp’s public agent tool contract and uses seed-backed state to preserve realistic cross-tool behavior, including approvals, receipt attachment, and spend metadata updates.

​
Quick Status

Run pnpm --filter @archal/fidelity status ramp for the current local state:
  • contract/runtime shape
  • fixture corpus size
  • replay-order and canonical-shape coverage
  • local build freshness for dist/index.js and dist/cli.js