Marqeta: the 360 agent-readiness check
Marqeta scores 56 of 100 on Ora's agent-readiness scan, a C, read 15 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, a command line. An MCP server on npm, with no handshake at /.well-known/mcp to announce it.
On 15 November 2026 the public site at marqeta.com scored 56 of 100 on Ora's 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: Marqeta offers discoverable developer resources and SDK packages, but lacks a published OpenAPI specification and WebMCP support.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 26.33 of 54 | 49% |
| Access | Can agents read it | 24 of 43 | 56% |
| Discovery | Can agents find and recommend it | 8 of 11 | 73% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 56 of 100 | 56% |
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. 2 checks in this group do not apply to this site and are left out.
Marqeta is not in the directory's edition of 4 November 2026: no source read for that run named an MCP endpoint for marqeta.com, so the MCP evidence here is Ora's alone. Its MCP server check reads partial.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 8.33 of 10 | First-party MCP server published by product org (npm, @marqeta/marqeta-mcp, 8779 score). Add live handshake at /.well-known/mcp for full credit. |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Pass | 8 of 8 | REST API documentation found at /api. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 4 of 4 | Documentation site found at https://www.marqeta.com |
| Developer portal developer-portal | Pass | 5 of 5 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Fail | 0 of 8 | No OpenAPI/Swagger specification found |
| 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 | Partial | 3 of 5 | OAuth mentioned in documentation at https://www.marqeta.com but no OAuth or OpenID Connect endpoint responded |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Partial | 0 of 8 | No WebMCP support detected on the homepage (scanned 25 of 25 same-origin script bundle(s) for modelContext registrations). WebMCP is mentioned in the documentation at /docs, but a mention is not an implementation, |
| 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: @marqeta/helloworld |
| JSON error responses json-error-responses | Fail | 0 of 3 | 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.
| 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 | 1 of 1 | 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 | 1 of 1 | 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 | 1 of 1 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://marqeta.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 1 of 1 | All 5 sampled pages are publicly readable (5 with substantive content) |
| 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. One check in this group does not apply to this site and is left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 3.33 of 5 | Homepage: 4649 chars with H1, but 4.9% content ratio is below the 5% target. 10 of 10 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Partial | 0 of 1 | 4 of 11 measured pages exceed ~25K tokens of extracted text: https://www.marqeta.com/docs/developer-guides/about-cards/ (~47K tokens), |
| Sitemap exists sitemap | Pass | 1 of 1 | Valid sitemap found at https://www.marqeta.com/sitemap.xml with 804 entries |
| llms.txt exists llms-txt-exists | Fail | 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting llms-txt-formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| 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://marqeta.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. |
| JSON-LD structured data json-ld | Partial | 1 of 2 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 0.5 of 1 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 0.5 of 1 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Metadata completeness metadata-completeness | Pass | 1 of 1 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 0.67 of 1 | When-to-use guidance found at https://www.marqeta.com |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | marqeta.com ranks #9 for "Marqeta" (searched your brand name alone: no main product term from your homepage qualified) |
| Developer resource discoverability agentic-search-specific | Pass | 4 of 4 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (2 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 marqeta.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 Marqeta, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- WebMCP support: partial, 0 of 8, about 6.6 points to gain. Ora saw: No WebMCP support detected on the homepage (scanned 25 of 25 same-origin script bundle(s) for modelContext registrations). WebMCP is mentioned in the documentation at /docs, but a mention is not an implementation, so it earns no points.
- OpenAPI spec published: fail, 0 of 8, about 6.2 points to gain. Ora saw: No OpenAPI/Swagger specification found
- Brand name discoverability: partial, 1 of 3, about 4 points to gain. Ora saw: marqeta.com ranks #9 for "Marqeta" (searched your brand name alone: no main product term from your homepage qualified)
- JSON error responses: fail, 0 of 3, about 2.5 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
- Scoped permissions: partial, 2 of 5, about 2.5 points to gain. Ora saw: Scoped permissions described at https://www.marqeta.com, but no machine-readable scope declaration found (OpenAPI oauth2 scopes or RFC 9728 scopes_supported)
Our read
Marqeta has shipped an MCP server and not yet hung it on the door. Ora found a first-party server on npm as @marqeta/marqeta-mcp, but no live handshake at /.well-known/mcp, which full credit needs. The rest of the act layer is mixed: REST documentation at /api scores 7 of 7 on the protocol check, a CLI package sits on npm as @marqeta/helloworld, and OAuth is described in the docs though no OAuth or OpenID Connect endpoint responded; Ora found no OpenAPI specification. The Usability layer reads about 26 of 54. The door is open to all four test agents, and robots.txt allows the AI search crawlers in 3 of 3 checks. The reading layer has a sitemap of 804 entries and no llms.txt, and 4 of 11 measured pages run past about 25K tokens. The fix worth most is WebMCP, about 6.6 points, which the docs already mention. A C at 56: the server is in the package registry, and the website has yet to point to it.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai 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 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.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.