Connect Ramp to Claude
Give Claude governed access to Ramp’s 124 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ramp to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Approve Ramp in Runlayer
Add Ramp from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Ramp’s 124 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to Ramp
Each user signs in to Ramp with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Ramp from Claude
Ramp’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
124 Ramp tools in Claude
Runlayer policy decides which of these Claude users can call.
Activate card
Activate a card by its last four digits.
Add traveler loyalty program
Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram.
Answer policy question
Get an answer to a question about the expense policy or funds (amount, restrictions, etc).
Approve or reject bill
Approve or reject a submitted bill that is pending approval.
Approve or reject reimbursement
Approve or reject an employee reimbursement request for an out-of-pocket expense.
Approve or reject request
Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval.
Approve or reject transaction
Approve or reject a transaction awaiting your review.
Cancel reimbursement payment
Cancel the payment on a reimbursement that has been approved but not yet paid out.
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Ramp call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more