---
title: "Ramp: the 360 agent-readiness check | Agent MCP Directory"
description: "Ramp on Ora's agent-readiness scan, read 2026-11-09: 68 of 100, grade C, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/ramp-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Ramp: the 360 agent-readiness check | Agent MCP Directory

> Ramp on Ora's agent-readiness scan, read 2026-11-09: 68 of 100, grade C, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/ramp-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# Ramp: the 360 agent-readiness check

Ramp scores 68 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 4: an OpenAPI specification, a public API, OAuth, a command line. A specification and a live server, under a product name that search does not return.

On 9 November 2026 the public site at ramp.com scored 68 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C, in Ora's Payments & Fintech category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Ramp offers comprehensive spend management APIs and SDKs, but lacks OAuth scoped permissions and JSON error standardization for agent integration.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 55 of 89 | 62% |
| Access | Can agents read it | 44 of 58 | 76% |
| Discovery | Can agents find and recommend it | 11 of 16 | 69% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 68 of 100 | 68% |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. One check in this group does not apply to this site and is left out.

In the directory, Ramp sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/ramp-com/). Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.ramp.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server referenced in llms.txt |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at /api. GraphQL endpoint at https://api.ramp.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.ramp.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at https://docs.ramp.com |
| OpenAPI spec published openapi-spec | Pass | 7 of 7 | OpenAPI spec found at https://ramp.com/openapi.json (version: 3.0.0) |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://mcp.ramp.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: @ramp/cli |
| Multi-language SDK packages rest-sdk-packages | Partial | 1 of 3 | SDK package found only in npm |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | No REST rate-limit headers found on probed endpoints (GraphQL signal: fail 0). |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | No REST Idempotency-Key support detected (GraphQL signal: fail 0). |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents. One check in this group does not apply to this site and is left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://ramp.com/. Declared policy only; |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Pass | 3 of 3 | 5206 chars, semantic headings (1 H1 + 14 H2s + 5 H3s), 6.0% content ratio |
| Page token budget page-token-budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~1K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://ramp.com/sitemap/root.xml with 162 entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Fail | 0 of 1 | None of the 162 sampled sitemap entries carries a lastmod date. Add <lastmod> (W3C datetime) so agents can prioritize fresh content. |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://ramp.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 83 lines with markdown links, 14,959 characters in total. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://ramp.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Partial | 1 of 2 | Agent mode view found at ?mode=agent (3 signals: api, agent, integration) |
| JSON-LD structured data json-ld | Partial | 2 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: og:type |
| Agent instruction / when-to-use agent-instruction | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. One check in this group does not apply to this site and is left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Fail | 0 of 3 | ramp.com was not in the top 10 for "Ramp spend management" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q123190361 (Ramp) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | No bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to ramp.com.

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Ramp, with what Ora observed. The wording of each fix is Ora's; [the 28 checks it runs on an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their layer and tier.

-   Brand name discoverability: fail, 0 of 3, about 4.2 points to gain. Ora saw: ramp.com was not in the top 10 for "Ramp spend management"
-   Scoped permissions: fail, 0 of 5, about 2.5 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
-   JSON error responses: fail, 0 of 4, about 2 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
-   Agent instruction / when-to-use: fail, 0 of 3, about 1.7 points to gain. Ora saw: No agent instruction file with when-to-use guidance found
-   REST typed error model: fail, 0 of 3, about 1.5 points to gain. Ora saw: No typed error model found in OpenAPI spec

## Our read

Ramp publishes most of what the act layer asks for: an MCP server at mcp.ramp.com/mcp that answers and requires authentication, OAuth authorization server metadata on the same host, an OpenAPI 3.0.0 specification at ramp.com/openapi.json, @ramp/cli on npm, a reachable GraphQL endpoint, an llms.txt at the root and a home page that reads as prose with one H1 and fourteen H2s at a 6 percent text ratio. The largest deduction is a search result: ramp.com was not in the top ten for its own product term, about 4.2 points. The rest are specification details, with no typed error model in the OpenAPI file, no declared scopes, and endpoints that do not answer errors as JSON. One probe, the WebMCP read of ramp.com/docs/api, was answered 403 by a bot shield and is unverified. A C that reads like a B with a search problem.

## Test your own surfaces

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/ramp-agent-readiness/index.md)

## Sources

-   [Ora's scan of ramp.com, GET /api/score (vendor)](https://ora.ai/api/score/ramp.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [ramp.com, the company's site](https://ramp.com/), read 9 November 2026

Last reviewed 9 November 2026